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/clarify)<a href="https://agentmods.dev/skills/idosreisjunior/sdd-claude-kit/clarify"><img src="https://agentmods.dev/badge/skills/idosreisjunior/sdd-claude-kit/clarify/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/idosreisjunior/sdd-claude-kit/clarify"><img src="https://agentmods.dev/badge/skills/idosreisjunior/sdd-claude-kit/clarify.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.00103 | $0.01437 |
| Opus 5 | $0.00051 | $0.00718 |
| Sonnet 5 | $0.00021 | $0.00287 |
| Haiku 4.5 | $0.00010 | $0.00144 |
Grade A, and why
clarify 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-kit:clarify — resolver ambiguidades
Transforma as questões pendentes de uma spec em decisões registradas, e promove a mudança para CLARIFIED quando não resta ambiguidade crítica.
disable-model-invocation: false é deliberado: clarify resolve questões a partir de respostas dadas na conversa e não age sobre decisão irreversível. Ver ADR-008.
A regra que governa esta skill
Não inventar respostas. Uma questão só sai da lista de pendentes quando o usuário a responde — na conversa ou na própria spec. Preencher uma questão com o que parece razoável é o mesmo defeito que o Artigo 2 proíbe para requisitos: uma suposição com aparência de decisão. Se a resposta não veio, a questão permanece, e a mudança não sai de DRAFT enquanto houver questão crítica aberta.
Modo de governança
Leia workflow.mode de .specs/config.yaml antes de agir.
| Modo | Comportamento desta skill |
|---|---|
advisory |
Informa as questões abertas e as respostas registradas; nunca bloqueia nem exige confirmação |
guided (padrão) |
Exige resposta explícita antes de resolver uma questão e confirmação antes de promover a CLARIFIED |
strict |
Ainda não implementado na Fase 1. Informe isso ao usuário 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.
Arquivos que esta skill lê
| Quando | O quê |
|---|---|
| Sempre | .specs/config.yaml — idioma e modo |
| Sempre | <dir-da-mudança>/spec.md — as questões pendentes e os requisitos |
| Sempre | <dir-da-mudança>/status.yaml — estado atual, blocked_by e resolved_questions |
| Se existir | .specs/project/glossary.md — para usar os termos do domínio nas respostas |
Não leia as specs de outras mudanças (Art. 7). A clarificação é sobre esta spec e as respostas dadas para ela.
Procedimento
1. Localizar a mudança e as questões
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.
- 8d ago First seen · 100 lines · 103 tokens per session scan A 1b3e05798dde
clarify is a skill published in the GitHub repository idosreisjunior/sdd-claude-kit (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,437 once invoked, about $0.0005 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…