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 tranhieutt/software_development_department --skill handoffgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/handoff)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/handoff"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/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/tranhieutt/software_development_department/handoff"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/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.00030 | $0.01771 |
| Opus 5 | $0.00015 | $0.00886 |
| Sonnet 5 | $0.00006 | $0.00354 |
| Haiku 4.5 | $0.00003 | $0.00177 |
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 7d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Generate the lightweight handoff summary (what was built, what's missing,
acceptance criteria) and, when needed, save a formal handoff artifact to
.tasks/handoffs/. The receiver verifies the summary before starting work.
Steps
1. Parse arguments
Extract from $ARGUMENTS:
| Positional | Required | Description |
|---|---|---|
<from-agent> |
yes | Sending agent name (e.g. backend-developer) |
<to-agent> |
yes | Receiving agent name (e.g. qa-engineer) |
<artifact> |
yes | Primary file or path being handed off |
[task_id] |
no | Task ID to link checkpoint — auto-detected from active checkpoint if omitted |
| Flag | Default | Description |
|---|---|---|
--risk |
Medium |
Risk tier: Low, Medium, High |
--status |
complete |
Artifact status: complete, partial, draft |
--criteria |
prompt | Acceptance criteria strings (can be multi-value) |
--formal |
off | Force writing a durable handoff file even when risk is not High |
If from-agent, to-agent, or artifact are missing, print usage and stop:
Usage: /handoff <from-agent> <to-agent> <artifact> [task_id] \
[--risk Low|Medium|High] \
[--status complete|partial|draft] \
[--criteria "criterion 1" "criterion 2"] \
[--formal]
Example:
/handoff backend-developer qa-engineer src/api/auth.ts 042 \
--risk Medium --criteria "POST /auth returns 201" "Invalid creds → 401"
Schema reference: .claude/docs/handoff-schema.md
2. Validate agents
Check that <from-agent>.md and <to-agent>.md exist in .claude/agents/.
If either is missing, warn but continue:
⚠️ Agent "<name>" not found in .claude/agents/ — check spelling.
3. Resolve task_id and context_snapshot
- If
task_idwas provided, check if.tasks/checkpoints/<task_id>.mdexists. If yes, setcontext_snapshotto that path. - If
task_idwas NOT provided, scan.tasks/checkpoints/for the most recently modified.mdfile (excluding.gitkeep) and use it as a suggestion. - If no checkpoint exists, set
context_snapshottonull.
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.
- 7d ago First seen · 212 lines · 30 tokens per session scan A c59d9400e9e3
handoff is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 1,771 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-09-03.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
tdd
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.
verify
Fresh verification gate before claiming done, fixed, passing, ready, or before commit/PR. Evidence before claims, always.