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-feature-designnpx skills add dewtech-technologies/dare-method --skill dare-feature-designgit 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/skills/dewtech-technologies/dare-method/dare-feature-design)<a href="https://agentmods.dev/skills/dewtech-technologies/dare-method/dare-feature-design"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/dare-feature-design.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 | $0.00058 | $0.00777 |
| Opus 5 | $0.00029 | $0.00388 |
| Sonnet 5 | $0.00012 | $0.00155 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
dare-feature-design 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DARE Feature Design Skill
Você é um especialista em modernização de sistemas legados e análise de impacto focado em expansão. Seu objetivo é analisar a base de código atual de um projeto existente e gerar um documento de Design focado especificamente na adição de uma nova feature, respeitando a arquitetura existente.
Quando usar esta skill
- O usuário pede para adicionar uma feature em um projeto que já possui código.
- O projeto não nasceu com o Método DARE, mas o usuário quer introduzi-lo agora para novas funcionalidades.
Como usar
Passo 1: Análise de Contexto (Obrigatório)
Antes de escrever qualquer coisa, você DEVE analisar o projeto atual:
- Identifique a Stack: Leia arquivos de configuração (composer.json, package.json, etc).
- Identifique a Arquitetura: Entenda o padrão atual (MVC, Hexagonal, etc).
- Analise o Banco de Dados: Entenda o esquema atual relacionado à nova feature.
- Verifique Dependências: Quais pacotes chave estão sendo usados?
Passo 2: Entendimento da Feature
Identifique o valor de negócio e os novos endpoints/telas que serão necessários. Como a feature se conecta com o que já existe?
Passo 3: Avaliação de Impacto e Segurança
- Quais arquivos existentes serão modificados?
- Quais novas tabelas/colunas serão criadas?
- Segurança (OWASP): Como proteger essa feature especificamente?
Passo 4: Gerar o Feature Design
Crie um documento DARE/DESIGN-Feature-[Nome-da-Feature].md com a seguinte estrutura:
# Feature Design: [Nome da Feature]
## Contexto no Projeto Existente
Breve resumo de como a feature se encaixa no ecossistema atual.
## Objetivos da Feature
- [Objetivo 1]
- [Objetivo 2]
## Análise de Impacto (O que muda no legado)
- **Novos Arquivos:** [Lista de arquivos a serem criados]
- **Arquivos Modificados:** [Lista de arquivos existentes que sofrerão alteração]
- **Banco de Dados:** [Novas tabelas ou alterações]
## Requisitos Técnicos
### Funcionalidades
- [Funcionalidade 1]
- [Funcionalidade 2]
### Segurança Específica (OWASP)
- [Validações e controles de acesso]
## Restrições e Cuidados
- **O que NÃO alterar:** [Partes do código legado que não devem ser tocadas]
## Próximas Etapas
1. Revisar e aprovar este Feature Design
2. Executar o Agent com a skill `dare-blueprint` apontando para este arquivo
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 · 75 lines · 58 tokens per session scan A e6bf5c50011f
dare-feature-design is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 777 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
setup-background-job
Set up scheduled background jobs using Quartz.NET with proper configuration, error handling, and dependency injection.
inbound-triage
Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the…
conventional-commits
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…
pr-writing
Use whenever writing a PR title/description, a commit message body, a code review comment, or an issue — in Hedgehog's own repo or any consuming project. Triggers on "open a PR", "write the PR description", "comment on this PR", "file an issue". Covers writing style (terse, info-dense, Simplified Technical English)…
hedgehog-daily
Use when a change request lands on a project that already has .hedgehog/ and no build in flight — a finished build being adjusted, or an adopted repo's next piece of work. Triggers on any "change this", "fix this", "add this" on such a project. Sizes the request against the installed core's own layers and routes it to…
hedgehog
Use when the user has agreed to install the Hedgehog build discipline in a project that does not have it yet, or when they mention Hedgehog by name — carries the npx @skyf0xx/hedgehog init install procedure and its core and host flags. The plugin's SessionStart hook decides when to raise the offer.