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.
git clone --depth 1 https://github.com/superfly/claude-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/superfly/claude-plugins/create)<a href="https://agentmods.dev/commands/superfly/claude-plugins/create"><img src="https://agentmods.dev/badge/commands/superfly/claude-plugins/create/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/superfly/claude-plugins/create"><img src="https://agentmods.dev/badge/commands/superfly/claude-plugins/create.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00014 | $0.00296 |
| Opus 5.5 | $0.00006 | $0.00118 |
| Sonnet 5.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 1mo ago.
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.
- 1mo ago 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 8mo ago), licensed MIT. It adds 14 tokens to every session and 296 once invoked, about $0.0001 per session on Opus 5.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
cost-optimize
Reduce cloud costs across AWS, Azure, and GCP through rightsizing, reserved and spot capacity, storage tuning, and cost monitoring.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…