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 igoruehara/spec-driven --skill kickoffgit clone --depth 1 https://github.com/igoruehara/spec-drivenWrote 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/igoruehara/spec-driven/kickoff)<a href="https://agentmods.dev/skills/igoruehara/spec-driven/kickoff"><img src="https://agentmods.dev/badge/skills/igoruehara/spec-driven/kickoff/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/igoruehara/spec-driven/kickoff"><img src="https://agentmods.dev/badge/skills/igoruehara/spec-driven/kickoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00195 | $0.02680 |
| Opus 5.5 | $0.00078 | $0.01072 |
| Sonnet 5.5 | $0.00039 | $0.00536 |
| Haiku 4.5 | $0.00019 | $0.00268 |
Grade A, and why
kickoff 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Kickoff de projeto (Lean Inception + SDD)
Você vai entrevistar, mapear, propor e gerar um roadmap. A primeira decisão é o modo: o trabalho para um projeto que está começando é diferente do de um projeto que já roda.
Princípios de condução
- Pergunte em lotes curtos com
AskUserQuestion(máx. 4 perguntas, 2-4 opções cada). Ofereça sempre um default "(Recomendado)" como primeira opção; aceite "Other" livre. Quando um eixo abrir uma decisão ramificada (escolhas que dependem umas das outras — ex.: arquitetura → bounded contexts → infra), troque o lote por uma sabatina: rode/clarificar. - Não invente decisões de arquitetura. Você propõe opções com trade-offs; quem decide é o usuário.
- Não levante nem proponha ferramentas aqui — isso é a skill
/integracoes. O kickoff só faz a oferta neutra (Fase 0.5) de conectar. Se a/integracoesjá rodou, aproveite os insumos puxados; senão, siga sem e deixe/integracoescomo item do roadmap. - Confirme um resumo antes de gerar arquivos. Gere tudo de uma vez no fim.
- O objetivo final dos dois caminhos é o mesmo: a constituição do projeto + um roadmap acionável para rodar com o time.
Fase 0 — Detectar o modo
- Inspecione o diretório: manifests (
package.json,pyproject.toml,go.mod…),src/com código real, histórico git, docs já preenchidos.- Só o boilerplate / repo vazio → provável greenfield.
- Código de produto existente → provável brownfield.
- Confirme com
AskUserQuestion: Greenfield (começando) · Brownfield (já rodando) · Híbrido (base existe, mas vamos repensar). Roteie conforme a resposta. - Leia
README.mdeCLAUDE.mdpara alinhar com a esteira SDD.
Fase 0.5 — Oferta de integração (neutra)
Conectar MCPs é ortogonal ao kickoff e é trabalho da skill /integracoes. Aqui você faz só
uma oferta neutra — não liste nem proponha ferramentas (quem levanta o ferramental é a
/integracoes; deixe o usuário dizer o que usa de fato lá).
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 · 138 lines · 195 tokens per session scan A 2a81e99be52c
kickoff is a skill published in the GitHub repository igoruehara/spec-driven (213 stars, last pushed 2mo ago), licensed MIT. It adds 195 tokens to every session and 2,680 once invoked, about $0.0008 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.