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-dna)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-dna"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-dna/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/dewtech-technologies/dare-method/dare-dna"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-dna.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.00000 | $0.01067 |
| Opus 5.5 | $0.00000 | $0.00427 |
| Sonnet 5.5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
dare-dna 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 1mo 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-dna
Camada semântica da extração de DNA do projeto. Roda depois do comando dare dna, que já varreu
o código e extraiu os fatos de convenção. Sua função é transformar fatos em regras acionáveis —
o "como esse codebase faz as coisas" que uma nova feature deve respeitar.
Equivalente no terminal:
dare dna --ai
Como usar
/dare-dna # preenche o PROJECT-DNA.md gerado por `dare dna`
Pré-requisito: rodar
dare dnaantes (geraDARE/PROJECT-DNA.mdeDARE/dna-facts.json). Usedare dna --astpara extração híbrida tree-sitter + regex (opt-in, v3.15+). Se não existirem, instrua o usuário a rodardare dnaprimeiro.
Quando usar
- Projeto legado que vai adotar o DARE para novas features, sem reescrever o existente.
- Acabou de rodar
dare dnae oPROJECT-DNA.mdtem seções<!-- AGENT -->em aberto. - O objetivo é um ruleset que faça o agente seguir o padrão da casa, não o default genérico.
O que fazer
1. Carregar os fatos (não re-varrer tudo)
- Leia
DARE/dna-facts.json— fonte determinística (tooling, naming, camadas, testes, libs, commits). - Abra 2-5 arquivos representativos por camada (um controller, um service, um model, um teste) para inferir os padrões que o CLI não detecta (tratamento de erro, validação, estilo de teste).
2. Preencher DARE/PROJECT-DNA.md
Substitua cada bloco <!-- AGENT: ... -->:
- Convenções de Nomenclatura — confirme o estilo detectado e documente exceções (ex.: componentes em PascalCase, utilitários em kebab).
- Arquitetura & Camadas — nomeie o padrão com confiança (MVC / Layered / Hexagonal) e escreva as regras de onde cada coisa mora (ex.: "controllers só orquestram; regra de negócio vai em services; acesso a dados só em repositories").
- Padrões de Teste — onde os testes ficam, naming, assertions reais (não
expect(true)), uso de mocks/fixtures. - Tratamento de Erros & Validação — como o projeto trata erros (exceptions, Result/Either, try/catch) e valida inputs. Dê exemplos concretos do código real.
- Regras de Ouro do Projeto — liste o que SEMPRE e o que NUNCA fazer neste codebase.
- ⚠️ Incertezas / Inconsistências — convenções ambíguas/misturadas que o humano precisa decidir.
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.
- 1mo ago First seen · 79 lines · 0 tokens per session scan A cfdbbb4ed8e1
dare-dna is a command published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,067 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.
validate
Command "validate" from Vimalk0703/shipworthy, covering /validate — pre-push validation gate, what this does, steps, when to run and output format.
retro
Command "retro" from Vimalk0703/shipworthy, covering process and important.
audit
Before executing this command, output.