Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add idosreisjunior/sdd-claude-kit/plugin install sdd-kitWrote 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/idosreisjunior/sdd-claude-kit/init)<a href="https://agentmods.dev/skills/idosreisjunior/sdd-claude-kit/init"><img src="https://agentmods.dev/badge/skills/idosreisjunior/sdd-claude-kit/init.svg" alt="Measured on agentmods" 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.00080 | $0.02903 |
| Opus 5 | $0.00040 | $0.01452 |
| Sonnet 5 | $0.00016 | $0.00581 |
| Haiku 4.5 | $0.00008 | $0.00290 |
Grade A, and why
init 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 6d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-kit:init — inicializar o framework
Cria a estrutura .specs/ em um projeto, depois de diagnosticar o que já existe ali.
disable-model-invocation: false é deliberado: init é o ponto de entrada e precisa ser descoberto por quem ainda não conhece o comando. Ver ADR-008.
Regras que valem durante toda a execução
Estas não são um passo do procedimento — valem do início ao fim.
- Nunca sobrescrever arquivo existente sem confirmação explícita do usuário. Vale para qualquer arquivo, dentro ou fora de
.specs/. - Nunca alterar arquivo de código. A detecção é somente leitura.
Editestá removido do conjunto de ferramentas justamente para tornar isso mecânico, não apenas uma instrução. - Escrever apenas dentro de
${CLAUDE_PROJECT_DIR}/.specs/. - Nunca inventar uma detecção. Sem evidência direta no repositório, o valor é
nullou vem marcado como hipótese. nullsignifica NÃO DETECTADO — jamais "aprovado".- Nenhuma requisição de rede. Nenhuma etapa desta skill acessa a internet.
- Todo texto apresentado ao usuário segue
project.language.
Modo de governança
O modo vem do argumento --mode, ou de guided como padrão. Ele é gravado em config.yaml e governa as skills seguintes.
| Modo | Comportamento desta skill |
|---|---|
advisory |
Informa o que detectou; nunca bloqueia |
guided (padrão) |
Informa e pede revisão do diagnóstico antes de criar os arquivos |
strict |
Ainda não implementado na Fase 1. Informe isso ao usuário, grave mode: strict em config.yaml como ele pediu, e opere como guided |
Nunca finja um bloqueio que não existe. Dizer que o modo strict impediu algo, quando ele não está implementado, é pior que não ter o modo — cria confiança em uma proteção ausente. O bloqueio efetivo depende dos hooks da Fase 4.
Arquivos que esta skill lê
Declarados explicitamente para não carregar o repositório inteiro:
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.
- 6d ago First seen · 217 lines · 80 tokens per session scan A d7a855056bae
init is a skill published in the GitHub repository idosreisjunior/sdd-claude-kit (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 2,903 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…