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 commands/hmaurus/masterclaude/pdir-criar-specgit clone --depth 1 https://github.com/hmaurus/masterclaudeWrote 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/commands/hmaurus/masterclaude/pdir-criar-spec)<a href="https://agentmods.dev/commands/hmaurus/masterclaude/pdir-criar-spec"><img src="https://agentmods.dev/badge/commands/hmaurus/masterclaude/pdir-criar-spec.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 | $0.00025 | $0.00520 |
| Opus 5 | $0.00013 | $0.00260 |
| Sonnet 5 | $0.00005 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
pdir-criar-spec 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 5d 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.
What it actually says
PDIR: Criar Spec
Cria um documento de especificação completo a partir de uma entrevista em profundidade com o usuário. Baseado no Interview Pattern documentado pela Anthropic.
Este comando NÃO planeja nem implementa. Ele produz apenas a spec — o input ideal para o plan-mode do Claude Code.
Em qualquer passo, se algo falhar ou faltar informação, informe o erro e pergunte ao usuário como prosseguir.
Processar $ARGUMENTS
Extrair do $ARGUMENTS:
- Descrição da demanda: o que o usuário quer construir
Se vazio: perguntar ao usuário o que ele quer construir.
Instruções
1. Explorar Contexto do Projeto
Ler CLAUDE.md, README.md e arquivos relacionados à demanda. Entender stack, padrões e estrutura existentes para fazer perguntas informadas.
2. Entrevistar o Usuário
Entrevistar o usuário em profundidade usando AskUserQuestion. Cobrir:
- Implementação técnica
- UI/UX
- Edge cases
- Preocupações
- Tradeoffs
Regras da entrevista:
- Focar nas partes difíceis que o usuário pode não ter considerado
- Ir fundo — se uma resposta revela complexidade, explorar antes de avançar
- Continuar até cobrir tudo — não encerrar prematuramente
3. Gerar Spec
Criar docs/projeto/specs/ se não existir.
Saída: docs/projeto/specs/spec-[nome-da-demanda].md
Escrever uma spec completa cobrindo tudo que foi discutido na entrevista. Formato livre — estruturar conforme fizer sentido para a demanda, sem template rígido.
4. Revisar com o Usuário
Apresentar a spec e perguntar se algo está faltando, errado ou ambíguo. Ajustar até o usuário aprovar.
5. Feedback Final
Spec criada!
Arquivo: docs/projeto/specs/spec-[nome].md
Próximos passos:
1. /clear — limpar contexto antes de implementar
2. Entrar em plan-mode e pedir para implementar a spec:
"Planeje e implemente a spec em docs/projeto/specs/spec-[nome].md"
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.
- 5d ago First seen · 65 lines · 25 tokens per session scan A f366a0cac581
pdir-criar-spec is a command published in the GitHub repository hmaurus/masterclaude (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 520 once invoked, about $0.0001 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.