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 skills add Dragoon0x/dragoon-skills --skill handoffgit clone --depth 1 https://github.com/Dragoon0x/dragoon-skillsWrote 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/dragoon0x/dragoon-skills/handoff)<a href="https://agentmods.dev/skills/dragoon0x/dragoon-skills/handoff"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/handoff/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/skills/dragoon0x/dragoon-skills/handoff"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/handoff.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.00112 | $0.00336 |
| Opus 5.5 | $0.00045 | $0.00134 |
| Sonnet 5.5 | $0.00022 | $0.00067 |
| Haiku 4.5 | $0.00011 | $0.00034 |
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 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
/handoff
Generates a handoff doc with codebase facts and conventions pre-loaded.
When to use
- Handing off a feature to another engineer
- Onboarding a new contributor
- Capturing the design system shape for documentation
- The user asks for "a handoff doc", "context for the next engineer", "design system summary"
What's in it
- Stack
- Top 8 colors with role and usage count (table)
- Type scale and font families
- Spacing grid
- Radius variants
- Motion durations and easings
- Existing components (sample of up to 25)
- Conventions for adding new code in this codebase
- A pre-merge checklist gated on /critique, /slop, /review
Run it
dragoon handoff # general handoff
dragoon handoff "user invites" --apply # specific feature
Output
.dragoon/handoff/handoff-{slug}.md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 40 lines · 112 tokens per session scan A d1f3a8e785b9
handoff is a skill published in the GitHub repository Dragoon0x/dragoon-skills (4 stars, last pushed 6mo ago), licensed MIT. It adds 112 tokens to every session and 336 once invoked, about $0.0004 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 skills, from other repositories
implement-github-feature
Design and implement a new feature or component from a GitHub issue. Use for net-new functionality, not bug fixes.
contributions-hub
GitHub community: discussions, moderation, contributor health, CLAs.
issue-tracker
GitHub issues: find, triage, review and respond, with written reports.
team-manager
GitHub org teams: create, staff, onboard, offboard and audit access.
fix-github-issue
Fix a GitHub issue by number. Use when asked to fix GitHub issues.
Dark Mode Bug Finder
Detect dark mode rendering issues including contrast failures, missing theme tokens, image inversions, and transition glitches across components.