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-migrate)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-migrate"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-migrate/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-migrate"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-migrate.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.01042 |
| Opus 5 | $0.00000 | $0.00521 |
| Sonnet 5 | $0.00000 | $0.00208 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
dare-migrate 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 8d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-migrate
Camada semântica da migração (Fase 2 brownfield). Roda depois de dare migrate, que já leu os
artefatos do reverse/dna e gerou os esqueletos. Sua função é escrever a estratégia de migração
e os cenários Gherkin de paridade reais — o contrato comportamental que garante uma reimplementação
fiel ao legado.
Equivalente no terminal:
dare migrate --ai
Como usar
/dare-migrate
Pré-requisito: rodar
dare migrate --to <stack>antes (geraDARE/MIGRATION/MIGRATION.md,migration-facts.jsoneparity/*.feature). Isso por sua vez exigedare reversejá executado.
Quando usar
- Projeto legado entendido (
reverse+dnafeitos) que será reimplementado em outra stack. - Acabou de rodar
dare migratee oMIGRATION.md/.featuretêm seções<!-- AGENT -->/# AGENT.
O que fazer
1. Carregar contexto (não re-varrer)
- Leia
DARE/MIGRATION/migration-facts.json(origem, alvo, módulos, blocking gaps). - Leia
DARE/IDEIA.md+DARE/REVERSE/module-*.md(o que cada módulo faz) eDARE/PROJECT-DNA.md(convenções). Abra arquivos-chave do legado só o necessário para inferir comportamento.
2. Preencher DARE/MIGRATION/MIGRATION.md
- Decisão de Paradigma — origem e alvo mudam de paradigma (procedural→OO, monólito→serviços)? Registre decisão + justificativa; se preservado, diga.
- Estratégia de Migração — big-bang vs. strangler/parallel-run; ordem dos módulos; feature flags.
- Registro de Risco — para cada blocking gap (🔴) pré-listado, escreva o tratamento; some os riscos de regressão/dados/performance + mitigações.
- Arquitetura-alvo — desenhe na stack-alvo, alinhada ao DNA (camadas/convenções) quando o paradigma for preservado; senão justifique a nova organização.
- Plano de Cutover & Rollback — passos de corte, validação de paridade (rodar os
.feature), critério de go/no-go e rollback.
3. Escrever os Gherkin de paridade (parity/<módulo>.feature)
- Um
Scenariopor fluxo observável do módulo, derivado do comportamento legado real (não invente).Givenestado inicial →Whenação →Thenresultado idêntico ao legado. - Inclua casos de borda e formatação que o legado garante (ex.: arredondamento monetário, máscaras).
- Esses
.featuresão o contrato de aceite da reimplementação na stack-alvo.
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.
- 8d ago First seen · 75 lines · 0 tokens per session scan A 0903eaf3e10c
dare-migrate is a command published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,042 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
test-suite
Run comprehensive test suite with coverage analysis.
test
Agentic end-to-end test orchestrator — drive web/macOS flows, evaluate UX rubric, reconcile issues.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
qa-automation
Set up a comprehensive test automation strategy.
qa-e2e
End-to-End tests with Playwright or Cypress.
/e2e
Generate and run end-to-end Playwright tests for critical user journeys. Captures screenshots, videos, and traces on failure.