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/owl-listener/designer-skills/handoffgit clone --depth 1 https://github.com/Owl-Listener/designer-skillsWhat 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.00027 | $0.00216 |
| Opus 5 | $0.00014 | $0.00108 |
| Sonnet 5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
handoff 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
/handoff
Generate a developer handoff package.
Steps
- Visual specs — Document all measurements and tokens using
handoff-specskill. - Interaction specs — Define states and behaviors using
handoff-specskill. - QA criteria — Create implementation checklist using
design-qa-checklistskill. - Review readiness — Verify against review criteria using
design-review-processskill. - Version — Tag the design version being handed off using
version-control-strategyskill. - Package — Compile all specs, assets, and notes.
Output
Complete handoff package with visual specs, interaction specs, asset list, QA checklist, and implementation notes.
Consider following up with /setup-workflow to establish the ongoing QA process.
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 · 17 lines · 27 tokens per session scan A 6686488410c8
handoff is a command published in the GitHub repository Owl-Listener/designer-skills (2,412 stars, last pushed 23d ago), licensed MIT. It adds 27 tokens to every session and 216 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-30.
Other commands, from other repositories
execute
Run the autonomous implementation loop.
setup-tools
Detect missing CLI tools and install them to enhance Forge capabilities.
help
Display the following help text to the user.
brainstorm
Command dispatcher for brainstorm.
perf
Runtime entry point for checking asset performance budgets, script preconnects, and load optimization. Part of the Quality & Audit lifecycle phase.
eg-new-feature
Build a new feature using the elephant/goldfish workflow — design doc, goldfish design check, implement, review, validate.