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/dewtech-technologies/dare-methodWrote 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/dewtech-technologies/dare-method/dare-reverse)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-reverse"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-reverse.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.00000 | $0.02028 |
| Opus 5 | $0.00000 | $0.01014 |
| Sonnet 5 | $0.00000 | $0.00406 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
dare-reverse 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 4d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-reverse
Camada semântica da engenharia reversa (Fase 0 / brownfield). Roda depois do comando
dare reverse, que já varreu o código e gerou os esqueletos. Sua função é preencher as
inferências que o CLI determinístico não faz: propósito, domínio, responsabilidades e os
diagramas de fluxo ("como a coisa funciona").
Equivalente no terminal:
dare reverse --ai· extração híbrida AST:dare reverse --deep --ast
Como usar
/dare-reverse # preenche os artefatos gerados por `dare reverse`
Pré-requisito: rodar
dare reverseantes (geraDARE/IDEIA.md,DARE/REVERSE/module-*.mdeDARE/REVERSE/reverse-facts.json). Se não existirem, instrua o usuário a rodardare reverseprimeiro.
Quando usar
- O usuário quer entender / documentar um projeto legado antes de adotar o DARE.
- Acabou de rodar
dare reversee os artefatos têm seções<!-- AGENT: ... -->em aberto. - O objetivo é gerar uma pré-arquitetura (
IDEIA.md) que depois viraDESIGN.md.
Marcação de confiança (obrigatória)
Ao preencher cada <!-- AGENT -->, marque cada afirmação com seu nível de confiança + evidência:
- 🟢 <claim>.+`arquivo:linha`— CONFIRMED: evidência direta no código.- 🟡 <claim>.+`arquivo:linha`— INFERRED: padrão/dedução; pode estar errado.- 🔴 <claim>. → ver gaps.md— GAP: não determinável pelo código.
Regra: só 🟢 com evidência direta; na dúvida, 🟡; sem base, 🔴 (e registre em gaps.md). Os fatos
estruturais (caminho, LOC, deps) já vêm pré-marcados 🟢 pelo CLI — não os altere.
O que fazer
1. Carregar os fatos (não re-varrer tudo)
- Leia
DARE/REVERSE/reverse-facts.json— é a fonte de fatos determinística (stack, módulos, LOC, grafo de dependências). Confie nela para o inventário; não reconte arquivos. - Para cada módulo, abra 2-5 arquivos representativos (entrypoints, controllers, services, models) — o suficiente para inferir responsabilidade e fluxo. Não leia o módulo 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.
- 4d ago First seen · 142 lines · 0 tokens per session scan A 366088182a0d
dare-reverse is a command published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,028 tokens. 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-09-03.
Other commands, from other repositories
context
Command "context" from Vimalk0703/shipworthy, covering process, 1. context infrastructure, 2. regression fence health, 3. session signals and 4. context completeness.
diagnose
Command "diagnose" from Vimalk0703/shipworthy, covering process, example output, project diagnosis report, critical (fix immediately) and high (fix soon).
health
Command "health" from Vimalk0703/shipworthy, covering part 1: plugin installation health and part 2: project health.
retro
Command "retro" from Vimalk0703/shipworthy, covering process and important.
validate
Command "validate" from Vimalk0703/shipworthy, covering /validate — pre-push validation gate, what this does, steps, when to run and output format.
audit
Before executing this command, output.