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-layered-design)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-layered-design"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-layered-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.1 | $0.00000 | $0.01150 |
| Opus 5 | $0.00000 | $0.00575 |
| Sonnet 5 | $0.00000 | $0.00230 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
dare-layered-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 3d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-layered-design
Enforce arquitetura estrita de 4 camadas (Handlers, Services, Repositories, Models) em projetos DARE — independente de linguagem.
Como usar
/dare-layered-design # audita projeto atual
/dare-layered-design lint # roda checks AP-01 a AP-06
/dare-layered-design scaffold <recurso> # gera CRUD com camadas corretas
As 4 camadas
Handler → Service → Repository → Model
(HTTP) (negócio) (I/O) (domínio)
Handler
- Recebe request, valida input, chama um Service, retorna response
- Nunca acessa Repository direto, nunca instancia Service com
new
Service
- Implementa uma operação de negócio (
RegisterUser,RefundPayment) - Orquestra Repositories
- Nunca sabe sobre HTTP, nunca faz SQL inline
Repository
- Abstrai persistência (DB, cache, API externa)
- Retorna Model ou primitivo
- Nunca retorna HTTP status, nunca lança exceção de domínio
Model
- Entidade pura do domínio
- Nunca importa Repository/Service/Handler
Métricas obrigatórias
| ID | Métrica |
|---|---|
| M-01 | 100% dos Services têm testes unitários (sem DB/HTTP real) |
| M-02 | 0% de chamadas Handler→Repository direto |
| M-03 | 100% dos Handlers usam injeção (sem new Service()) |
| M-04 | 100% dos Repositories são agnósticos das camadas superiores |
Tabela por linguagem
| Camada | Laravel | NestJS | FastAPI | Rails | Rust | Go |
|---|---|---|---|---|---|---|
| Handler | Http/Controllers/ |
*.controller.ts |
routers/ |
app/controllers/ |
handlers/ |
handlers/ |
| Service | Services/ |
*.service.ts |
services/ |
app/services/ |
services/ |
services/ |
| Repository | Repositories/ |
*.repository.ts |
repositories/ |
app/repositories/ |
repositories/ |
repositories/ |
| Model | Models/ |
entities/ |
models/ |
app/models/ |
domain/ |
models/ |
Antipatterns
| AP | Antipattern | Sinal |
|---|---|---|
| AP-01 | Handler→Repository direto | controller.repo.find() |
| AP-02 | Service com SQL inline | db.query() em Service |
| AP-03 | Repository lança exceção de domínio | throw UserNotFound |
| AP-04 | Model importa Service | acoplamento invertido |
| AP-05 | God Service (>20 métodos) | UserService.everything() |
| AP-06 | Fat Controller (>100 linhas) | lógica em Handler |
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.
- 3d ago First seen · 125 lines · 0 tokens per session scan A 6e4ed717e33a
dare-layered-design is a command published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,150 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
contract-version-bump
Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog entry, downstream drift.
dev-supabase
Configure and use Supabase as a backend (Auth, Database, Storage, Realtime, Edge Functions).
api-gen
Generate REST API endpoints with routes, validation, error handling, and tests.
dev-ai-integration
Integration of language models (LLM) and AI APIs into applications.
dev-api
Create or document REST, GraphQL, or tRPC endpoints, with a versioning strategy.
dev-error-handling
Implements a robust and consistent error handling strategy.