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 skills/dewtech-technologies/dare-method/dare-migratenpx skills add dewtech-technologies/dare-method --skill dare-migrategit clone --depth 1 https://github.com/dewtech-technologies/dare-methodWhat 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 | $0.00063 | $0.00940 |
| Opus 5 | $0.00032 | $0.00470 |
| Sonnet 5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DARE Migrate Skill — Migração com paridade (brownfield Fase 2)
Equivalente no terminal:
dare migrate --ai
Você é o agente que transforma o entendimento do legado em um plano de migração com paridade.
Esta skill é a camada semântica: roda depois do comando 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.
Pré-requisito: o comando
dare migrate --to <stack>precisa ter rodado antes (geraDARE/MIGRATION/MIGRATION.md,migration-facts.json,parity/*.feature). Que por sua vez exigedare reversejá executado. Se faltar, peça ao usuário para rodar na ordem.
Quando usar esta skill
- Projeto legado entendido (
reverse+dna) que será reimplementado em outra stack. - Acabou de rodar
dare migratee há seções<!-- AGENT -->/# AGENTem aberto.
Passo a passo
1. Carregar contexto (não re-varrer)
Leia migration-facts.json (origem/alvo/módulos/blocking gaps), IDEIA.md + REVERSE/module-*.md
e PROJECT-DNA.md. Abra arquivos-chave do legado só o necessário para inferir comportamento.
2. Preencher DARE/MIGRATION/MIGRATION.md
- Decisão de Paradigma — mudou (procedural→OO, monólito→serviços)? Decisão + justificativa.
- Estratégia — big-bang vs. strangler/parallel-run; ordem dos módulos; feature flags.
- Registro de Risco — tratar cada blocking gap (🔴) + riscos de regressão/dados/performance.
- Arquitetura-alvo — na stack-alvo, alinhada ao DNA quando o paradigma for preservado.
- Cutover & Rollback — passos, validação de paridade (rodar
.feature), go/no-go, rollback.
3. Gherkin de paridade (parity/<módulo>.feature)
Um Scenario por fluxo observável, derivado do comportamento legado real: Given → When →
Then idêntico ao legado. Inclua bordas/formatos (arredondamento, máscaras). É 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.
- 2d ago First seen · 65 lines · 63 tokens per session scan A 71d95e9a32ad
dare-migrate is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 940 once invoked, about $0.0003 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 skills, from other repositories
write-test-plan
Generate a QA/UAT test plan from product specifications and task definitions, covering acceptance testing, integration flows, and exploratory testing. Unit tests are out of scope (handled by write-unit-tests skill).
implement-telegram-bot
Implement Telegram bot interactions with command handlers, message parsing, and inline keyboards for conversational interfaces.
setup-background-job
Set up scheduled background jobs using Quartz.NET with proper configuration, error handling, and dependency injection.
write-unit-tests
Write comprehensive unit tests with proper setup, assertions, and coverage of happy paths, edge cases, and error scenarios.
blazor-component-design
Design Blazor components with proper parameter binding, event callbacks, lifecycle management, and render optimization. Use when creating new Blazor Server or WASM components, refactoring component hierarchies, implementing cascading values, or optimizing component rendering performance.
hedgehog-planning-intake
Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…