# Create Custom Codex Pets From Reference Images

Creating a custom Codex pet requires a correctly sized sprite atlas and manifest. This skill combines RunComfy image generation with ImageMagick assembly and local installation.

## Install

```bash
npx skillstore add prime-skills/codex-pet
```

## Metadata

- Status: approved
- Slug: prime-skills-codex-pet
- Skillstore revision: r1
- Version status: missing
- Tree hash: 88f96bc7301b4395cba49a87f9307dad2423d79b0eb47c8d170ceb7a661470f2
- Author: prime-skills
- GitHub username: prime-skills
- License: MIT
- Repository: https://github.com/prime-skills/runcomfy-agent-skills/tree/fca19ae084c2ae4667f5c8affbb99da5103d5832/codex-pet
- Ref: ecf01ea0d94c8cbd4df454171b84d2c2ce76f5f1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/prime-skills-codex-pet
- Manifest: https://skillstore.pages.dev/api/skills/prime-skills-codex-pet/manifest

## Capabilities

- Generate one canonical sprite from a publicly accessible reference image through the RunComfy GPT Image 2 edit endpoint.
- Remove a solid chroma-key background and normalize the sprite into a transparent 192x208 cell.
- Build nine animation rows using shifts, rotations, blink overlays, mirroring, and transparent trailing cells.
- Assemble a 1536x1872 sprite atlas and convert the PNG output to WebP.
- Write pet.json and copy it with spritesheet.webp into the configured Codex custom asset directory.
- Adjust movement offsets and rotation values by editing the documented animation recipes.

## Use Cases

- Personalize a Coding Workspace: Create a custom Codex companion from an approved reference image and install its generated assets locally.
- Prototype a Mascot Animation: Convert a mascot reference into the documented nine-state atlas and experiment with subtle movement settings.
- Prepare Repeatable Asset Generation: Adapt the documented single-image workflow for several approved references, using separate names, working directories, and one model call per reference.

## Prompt Templates

### Beginner: Check Prerequisites

```
Check prerequisites for this Codex pet workflow. Report missing tools without installing software, reading tokens, or making a model call.
```

### Intermediate: Generate a Custom Companion

```
Create a Codex pet from [approved HTTPS image URL], named [simple-name]. Confirm third-party processing before generation and ask before installation or overwriting files.
```

### Advanced: Tune Existing Animation

```
Use the existing canonical cell in [working directory]. Increase jump height and review tilt without changing atlas dimensions, frame counts, or transparent trailing cells.
```

### Expert: Plan Controlled Batch Generation

```
Adapt this workflow for [approved image URLs]. Validate names, isolate outputs, safely encode metadata, and stop on failures. Confirm costs before model calls.
```

## Limitations

- Requires RunComfy authentication, network access, ImageMagick, and a publicly fetchable HTTPS source image; the source is processed by RunComfy.
- Animation derives from one pose and small image transforms, not distinct model-generated action frames.
- Background removal can erase similar subject colors, and image generation can alter identifying details.
- The supplied shell examples do not validate custom names or safely encode arbitrary metadata; review names and descriptions before execution.

## Best Practices

- Use an image you may share with RunComfy, and confirm authentication and expected charges before the model call.
- Use simple names without path separators, verify destination containment, and approve replacement of existing assets.
- Inspect transparency, atlas dimensions, frame counts, and identifying details before installing the generated files.

## Anti Patterns

- Using sensitive source images or placing authentication tokens in prompts, shared commands, or published output.
- Passing unvalidated path-like names or unescaped free-form metadata directly into the supplied shell examples.
- Expecting dramatic action sequences from one pose or changing the fixed atlas layout without checking compatibility.

## Security Audit

- Audited at: 2026-11-01T14:40:57.533\+00:00
- Summary: All 83 static alerts are false positives involving Markdown, ordinary commands, documentation links, configuration paths, or authentication terminology. One semantic risk remains: customizable names lack path validation before artifact creation and installation. No evidence found of malicious prompt injection or credential theft; the documented workflow sends the source image to RunComfy.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0