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 skills/jtsternberg/claude-plugins/sol-delegatenpx skills add jtsternberg/claude-plugins --skill sol-delegategit clone --depth 1 https://github.com/jtsternberg/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/skills/jtsternberg/claude-plugins/sol-delegate)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/sol-delegate"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/sol-delegate.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00591 |
| Opus 5 | $0.00021 | $0.00296 |
| Sonnet 5 | $0.00008 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
sol-delegate 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sol: Delegate the Doing
Use Sol's scarce frontier-model attention for decisions, not routine execution. Keep ownership of the outcome while routing mechanical work to a cheaper or more appropriate Codex model.
Keep in Sol
- Understand the user's actual goal and define the work shape.
- Make architecture, scope, risk, and trade-off decisions.
- Write prompts that give delegated work a concrete contract.
- Review delegated output critically against the goal.
- Resolve ambiguity that genuinely requires the main agent's judgment.
- Communicate decisions, evidence, and remaining risks to the user.
Delegate
Route file searches, routine edits, test runs, mechanical refactors, documentation passes, and bounded research to another available model. Prefer Terra for normal execution, GPT-5.5 or GPT-5.4 when the delegated task needs more reasoning, and Luna when direct model selection becomes available.
When direct Luna selection is unavailable, use Hotline/cmux only if that path is already configured and the user has put it in scope. Do not pretend a model switch occurred merely because the task was described as a Luna assignment.
Write the work order
Every delegation prompt must state:
- The outcome to produce.
- The files or surfaces in scope.
- Constraints, including files or actions to leave untouched.
- The checks or evidence required before reporting completion.
- What the delegated agent must report back.
Delegate independent tasks separately when their outputs can be reviewed independently. Keep dependent work in sequence so the next agent receives the verified result of the previous step.
Review the result
Treat delegated output as evidence, not authority. Inspect the diff or artifact, run the load-bearing checks, and verify the behavior at the surface the user actually cares about. If the delegated agent found a broader class of problem, follow that diagnosis instead of accepting the narrow patch.
Do not delegate the final judgment about whether the user's goal is met. Do not end with a report that merely says another model changed files; report what changed, what was verified, and what remains uncertain.
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.
- 4d ago First seen · 55 lines · 42 tokens per session scan A 2f4be9573993
sol-delegate is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 591 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…