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/rules/dewtech-technologies/dare-method/skill-feature-design)<a href="https://agentmods.dev/rules/dewtech-technologies/dare-method/skill-feature-design"><img src="https://agentmods.dev/badge/rules/dewtech-technologies/dare-method/skill-feature-design/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/rules/dewtech-technologies/dare-method/skill-feature-design"><img src="https://agentmods.dev/badge/rules/dewtech-technologies/dare-method/skill-feature-design.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.00619 |
| Opus 5.5 | $0.00000 | $0.00248 |
| Sonnet 5.5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
skill-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 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Feature Design para Projetos Existentes
Objetivo
Esta skill ensina você (a IA) a analisar o contexto de um projeto que já existe e planejar a inserção de uma nova feature de forma segura, isolada e respeitando os padrões já estabelecidos.
Quando Usar
- Quando o usuário pede para adicionar uma funcionalidade nova em um projeto existente.
- Quando o comando
/generate-feature-designfor invocado.
Como Analisar o Projeto Existente
O primeiro passo é sempre entender o que já existe antes de propor qualquer coisa nova.
Identifique a Stack e Arquitetura: Leia os arquivos de configuração do projeto (composer.json, package.json, etc.) para entender o framework, versão e padrão arquitetural (MVC, Hexagonal, CQRS). Se o projeto usa um padrão específico, a nova feature deve seguir esse padrão.
Analise o Banco de Dados: Leia as migrations ou esquemas existentes para entender as tabelas relacionadas à feature solicitada. Identifique se serão necessárias novas tabelas ou apenas novas colunas.
Verifique Dependências Chave: Entenda quais bibliotecas de terceiros já estão em uso (ex: Sanctum para auth, Spatie para permissões) e que podem ser aproveitadas pela nova feature.
Como Gerar o Design da Feature
O documento DARE/DESIGN-Feature-[Nome].md deve ser focado e conciso. Ele não descreve o sistema inteiro, apenas o impacto da nova feature.
| Seção | Conteúdo |
|---|---|
| Contexto | Como a feature se conecta ao que já existe |
| Novos Arquivos | Controllers, Models, Services a serem criados |
| Arquivos Modificados | O que muda no código legado |
| Banco de Dados | Novas tabelas ou colunas |
| Segurança | Proteções OWASP específicas para a feature |
| Restrições | O que não pode ser tocado |
Regras de Ouro
- Siga o Padrão Local: Se o projeto usa um padrão antigo ou específico, adapte a feature a ele, a menos que o usuário solicite refatoração explícita.
- Isolamento: Mantenha o impacto da feature o mais isolado possível para minimizar o risco de quebrar o sistema legado.
- Testes Nascem com a Feature: Se o projeto não tem testes, a nova feature DEVE nascer com testes isolados (Validation Gates do Ralph Loop).
- Segurança Inegociável: Mesmo que o código legado seja inseguro, a nova feature DEVE aplicar regras OWASP.
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 · 44 lines · 619 tokens per session scan A fd682983b4d5
skill-feature-design is a cursor rule 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 619 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 cursor rules, from other repositories
beads
This project uses Beads (bd) for issue tracking.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.