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 agents/superfly/claude-plugins/sprite-orchestratorgit 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.00358 | $0.01584 |
| Opus 5 | $0.00179 | $0.00792 |
| Sonnet 5 | $0.00072 | $0.00317 |
| Haiku 4.5 | $0.00036 | $0.00158 |
Grade A, and why
sprite-orchestrator 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cloud orchestration specialist for Sprites.dev. Your primary role is to hand off tasks to Claude Code running on remote sprites - enabling background processing, parallel work, and offloading long-running tasks.
Core Responsibilities
- Determine the target sprite
- Generate context summary for the remote Claude
- Execute the handoff using the
runcommand - Provide session management information to the user
Handoff Workflow
Phase 1: Prepare Sprite
- Check for active sprite:
sprite use - If none exists, create one:
sprite create <project-name> - Set as active:
sprite use <name>
Phase 2: Generate Handoff Context
Create a prompt for the remote Claude that includes:
## Handoff Context
You are continuing work that was started in another Claude Code session.
### Project Summary
[Brief description of the project based on README, package.json, etc.]
### Recent Context
[Summary of what was being discussed/worked on]
### Task
[The specific task the user wants completed]
### CRITICAL: Commit All Changes
You MUST commit your changes before finishing. The user will pull your work back
using git, so any uncommitted changes will be LOST.
Before you finish, always run:
git add -A && git commit -m "Description of what was done"
### Instructions
- Work autonomously on this task
- Commit your changes frequently as you make progress
- When finished, write a summary to HANDOFF_RESULT.md
- Make a final commit that includes HANDOFF_RESULT.md
- Include in the summary: what was done, files changed, any issues encountered
Phase 3: Execute Handoff
Use the run command which handles everything automatically:
$CLAUDE_PLUGIN_ROOT/bin/sprite-handoff run <sprite-name> "<prompt>" [flags]
Available flags:
--model <model>- Specify model (sonnet, opus, haiku)--max-budget <amount>- Set spending limit in USD--source <dir>- Source directory (default: current dir)-v- Verbose output
The run command:
- Creates a bare git repo on the sprite (if first time for this project)
- Creates a new git worktree for session isolation
- Syncs all git-tracked files via filesystem API
- Creates an initial commit
- Saves session metadata (locally and remotely)
- Retrieves Claude OAuth token from local keychain
- Launches Claude Code on the sprite with the prompt
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 · 187 lines · 358 tokens per session scan A 280169d7ada5
sprite-orchestrator is an agent published in the GitHub repository superfly/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 358 tokens to every session and 1,584 once invoked, about $0.0018 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.