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/igoruehara/spec-driven/handoffnpx skills add igoruehara/spec-driven --skill handoffgit clone --depth 1 https://github.com/igoruehara/spec-drivenWhat 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.00077 | $0.00722 |
| Opus 5 | $0.00039 | $0.00361 |
| Sonnet 5 | $0.00015 | $0.00144 |
| Haiku 4.5 | $0.00008 | $0.00072 |
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 2d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Handoff de sessão (pause / resume)
Mantém a continuidade do projeto via docs/STATE.md — a memória de trabalho volátil
(diferente do ADR, que é decisão durável). Detecte a intenção pelo pedido ou pergunte.
Modo PAUSE (pausar / encerrar)
Atualize docs/STATE.md com o estado real desta sessão:
- Em andamento / próximo passo — a feature/spec ativa e a próxima ação concreta (específica: "implementar AC-3 no adapter X", não "continuar a feature").
- Decisões recentes — o que foi decidido. Se for difícil de reverter, crie/atualize o ADR e linke; o STATE só resume.
- Bloqueios — o que trava e quem/como destrava.
- Ideias adiadas / todos — o que ficou de fora de propósito, com o gatilho para reconsiderar.
- Consolide
docs/lessons.md(condicional — só se houve aprendizado): a captura das lições é inline durante o trabalho, não aqui. No handoff você revisa e poda: alguma lição duplicada? alguma já estabilizou → promova pro destino durável (ADR / glossary /CLAUDE.md/ TESTING) e remova delessons.md, deixando só o link em "Promovidas". Não force entradas vazias. - Marque a data e o autor. Se houver
SPEC_DEVIATIONaberto, registre como bloqueio. - Ofereça um commit (
docs: handoff — atualiza STATE) se for repositório git.
Seja conciso e acionável. O STATE é para alguém (ou um agente) retomar frio amanhã.
Modo RESUME (retomar)
- Leia
docs/STATE.mde aspec.md/tasks.mdda feature ativa citada nele. - Se houver MCP conectado e relevante (Jira/Confluence), e a trava de conta estiver validada, atualize o contexto com o que mudou lá fora.
- Resuma onde paramos em poucas linhas: feature ativa, último passo, bloqueios abertos.
- Proponha o próximo passo (o "Em andamento / próximo passo" do STATE) e confirme com o usuário antes de executar.
Regras
- STATE.md é volátil; ADR é durável. Não escreva decisão estrutural só no STATE.
lessons.mdé staging: no handoff só consolida/poda — a captura é inline durante o trabalho. Lição que estabilizou tem que sair de lá; se está só crescendo, a poda falhou.- Não invente progresso: relate fielmente o que foi feito, o que falta e o que está bloqueado.
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.
- 2d ago First seen · 41 lines · 77 tokens per session scan A 503d1833b27a
handoff is a skill published in the GitHub repository igoruehara/spec-driven (213 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 722 once invoked, about $0.0004 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 skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.