Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/superfly/claude-plugins/creategit clone --depth 1 https://github.com/superfly/claude-pluginsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00014 | $0.00296 |
| Opus 5 | $0.00007 | $0.00148 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
create scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Create or Select a Sprite
Create a new Sprites.dev cloud sandbox or select an existing one as the active sprite for this project.
Behavior
If a sprite name is provided:
- Check if sprite exists with
sprite list - If it exists, set it as active with
sprite use <name> - If it doesn't exist, create it with
sprite create <name>then set as active
If no sprite name is provided:
- List existing sprites with
sprite list - Show the list to the user
- Ask if they want to use an existing sprite or create a new one
Commands to Use
# List sprites
sprite list
# Create new sprite
sprite create <name>
# Set active sprite for current directory
sprite use <name>
# Check current active sprite
sprite use
Output
After completing, report:
- Sprite name
- Whether it was created or already existed
- Confirm it's set as active
Tips
- Sprite names should be lowercase, alphanumeric with hyphens
- Sprites auto-hibernate after 30 seconds of inactivity (no cost when idle)
- Sprites have persistent filesystems - data survives hibernation
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 53 lines · 14 tokens per session scan A e4de5385ea52
create is a command published in the GitHub repository superfly/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 296 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.