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.
git clone --depth 1 https://github.com/bittencourtthulio/expxdevWrote 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/bittencourtthulio/expxdev/prodx-briefing)<a href="https://agentmods.dev/commands/bittencourtthulio/expxdev/prodx-briefing"><img src="https://agentmods.dev/badge/commands/bittencourtthulio/expxdev/prodx-briefing/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/commands/bittencourtthulio/expxdev/prodx-briefing"><img src="https://agentmods.dev/badge/commands/bittencourtthulio/expxdev/prodx-briefing.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.00029 | $0.00628 |
| Opus 5.5 | $0.00012 | $0.00251 |
| Sonnet 5.5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
prodx-briefing 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 today.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use a skill prodx, etapa P5, parte do briefing, seguindo references/05-veredito.md.
O pedido está em $ARGUMENTS — PD-ID. Se vier vazio, liste os vereditos assinados sem briefing e pergunte qual.
Verificação bloqueante — faça primeiro
Abra o VEREDITO.md e confirme as duas condições:
vereditoéfazeroufazer_outra_coisaaprovado_poreaprovado_emestão preenchidos por uma pessoa, não comoPENDENTE
Se aprovado_por estiver PENDENTE, não gere o briefing. Regra 2. Responda em uma linha explicando o bloqueio e ofereça colher a assinatura agora — ela é uma frase, não um processo.
Nunca preencha aprovado_por por conta própria, com o nome da skill, ou com o nome do dev que rodou o comando.
Destino
| Classificação | Destino | Formato |
|---|---|---|
novo, melhoria |
sprintx | briefing de feature, entrada da F1 |
correcao |
runx | briefing de ocorrência, vira 00-OCORRENCIA.md |
Consulte references/integracao/sprintx.md ou references/integracao/runx.md para o mapeamento de campos.
Conteúdo
De assets/TEMPLATE-BRIEFING.md:
- O problema — não a solução pedida (regra 4). Se o veredito foi
fazer_outra_coisa, é o problema reformulado. - O escopo mínimo aprovado — o do P4, literal.
- O que está explicitamente fora.
- Critérios de aceite do ponto de vista do negócio.
- Link para o veredito — PD-ID e caminho.
Regra 10 — nenhuma decisão técnica
Arquitetura, camada, tecnologia, tabela, biblioteca e padrão de projeto são do sprintx e do runx. Se o briefing mencionar arquivo, tabela ou tecnologia fora da seção de contexto, reescreva.
O prodx também não estima esforço: isso é a F3.5 do sprintx.
Caminho da triagem
Pedido aprovado na triagem entrega um briefing de uma linha, direto no INDICE.md, sem criar arquivo:
<PD-ID> | <classificacao> | <problema em uma linha> | aprovado por: <nome>, <data> | <destino>
Ao terminar
Atualize trabalho_gerado no frontmatter do VEREDITO.md e na linha do INDICE.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.
- today First seen · 56 lines · 29 tokens per session scan A 569db0045a2e
prodx-briefing is a command published in the GitHub repository bittencourtthulio/expxdev (3 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 628 once invoked, about $0.0001 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-11-07.
prodx-briefing compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| prodx-briefingbittencourtthulio/expxdev | Command | 3 | 1mo ago | MIT | A | 29 | Claude Code |
| memoryopensolon/soloncode | Command | 198 | 5d ago | MIT | A | 18 | Claude Code |
| dayreportFakeHank/ai-report-to-me | Command | 9 | 8mo ago | MIT | A | 0 | Claude Code |
| qtreportFakeHank/ai-report-to-me | Command | 9 | 8mo ago | MIT | A | 0 | Claude Code |
| modernize-transformfuxicodex/Fuxi | Command | 3.2k | 17d ago | none | A | 17 | Claude Code |
| searchcoltonbearden/carrel | Command | 2 | 3d ago | MIT | A | 29 | Claude Code |
| doctorfatihkan/badi | Command | 7 | 1mo ago | MIT | A | 0 | Claude Code |