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-proxima-demandagit 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-proxima-demanda)<a href="https://agentmods.dev/commands/hmaurus/masterclaude/pdir-proxima-demanda"><img src="https://agentmods.dev/badge/commands/hmaurus/masterclaude/pdir-proxima-demanda.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.00027 | $0.00640 |
| Opus 5 | $0.00014 | $0.00320 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
pdir-proxima-demanda 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PDIR: Próxima Demanda
Analisa o contexto da sessão atual, o plano do projeto e as Issues do GitHub para sugerir a próxima demanda a implementar. Ideal para ser executado logo após concluir uma demanda, aproveitando o contexto fresco antes do /clear.
Em qualquer passo, se algo falhar ou faltar informação, informe o erro e pergunte ao usuário como prosseguir.
Processar $ARGUMENTS
$ARGUMENTS (opcional): caminho para PRD. Se não fornecido, usar docs/projeto/PRD.md como padrão.
Instruções
1. Analisar Contexto da Sessão Atual
Resumir brevemente o que foi feito nesta sessão:
- Qual demanda foi implementada
- Quais arquivos foram criados ou modificados
- Qual área do projeto foi alterada (ex: auth, API, UI, infra)
2. Buscar Plano do Projeto
Se $ARGUMENTS fornecido → usar como caminho do documento.
Se não → usar docs/projeto/PRD.md.
Se o arquivo existir, ler e identificar:
- Demandas já concluídas (marcadas com
[x]ou similar) - Demandas pendentes (
- [ ]) - Ordem de prioridade/dependência
Se o arquivo não existir, pular para o passo 3.
3. Verificar Specs e Issues
# Specs existentes
ls docs/projeto/specs/ 2>/dev/null
# Issues abertas
gh issue list --state open --limit 30 --json number,title,labels
# Issues fechadas recentemente
gh issue list --state closed --limit 10 --json number,title
Identificar:
- Specs pendentes (sem sufixo
_concluida) - Specs concluídas (com sufixo
_concluida) - Issues abertas sem spec correspondente
4. Sugerir Próxima Demanda
Considerar:
- Dependências: o que a demanda recém-implementada desbloqueou
- Ordem lógica: seguir a sequência do PRD
- Specs pendentes: priorizar demandas que já têm spec escrita
- Prioridade natural: infra/config → modelos/types → lógica → API → UI
Apresentar a sugestão com:
- Título descritivo
- Justificativa breve de por que esta é a próxima demanda lógica
- Alternativas (se houver 1-2 opções viáveis)
5. Feedback Final
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 · 82 lines · 27 tokens per session scan A 4fce76978880
pdir-proxima-demanda is a command published in the GitHub repository hmaurus/masterclaude (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 640 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.