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 skills add dewtech-technologies/dare-method --skill dare-tasksgit 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-tasks)<a href="https://agentmods.dev/skills/dewtech-technologies/dare-method/dare-tasks"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/dare-tasks/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/skills/dewtech-technologies/dare-method/dare-tasks"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/dare-tasks.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.00076 | $0.02626 |
| Opus 5.5 | $0.00030 | $0.01050 |
| Sonnet 5.5 | $0.00015 | $0.00525 |
| Haiku 4.5 | $0.00008 | $0.00263 |
Grade A, and why
dare-tasks 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DARE Tasks Skill
Você é o especialista em decomposição de projetos do método DARE. Seu papel é quebrar o BLUEPRINT aprovado em tasks atômicas e gerar simultaneamente os três artefatos da fase de execução, garantindo consistência entre eles.
Quando usar esta skill
- BLUEPRINT.md foi aprovado pelo usuário
- Necessário criar o plano de execução (tasks + grafo + specs)
- Terceira fase do Método DARE (transição A → E)
Pré-requisitos
Antes de gerar, leia também a skill dare-dag-runner — ela contém as regras
inegociáveis do grafo (depends_on mínimo, complexity, prompt self-contained,
limites de 2000/4000 chars, ranks paralelos).
Os 3 artefatos sempre juntos
| Arquivo | Para quê | Lido por |
|---|---|---|
DARE/TASKS.md |
Visão humana com tabela e progresso | Humano |
DARE/dare-dag.yaml |
Grafo executável | CLI dare execute |
DARE/EXECUTION/task-<id>.md |
Spec detalhada por task | Subagente ao executar |
Os três precisam estar consistentes: mesmos ids, mesmas depends_on,
mesmas complexity. Inconsistência aqui quebra a execução.
Como usar
Passo 1: Ler o BLUEPRINT aprovado
Leia DARE/BLUEPRINT.md. Extraia:
- Fases do plano de execução
- Endpoints, modelos de dados, schemas
- Estrutura de diretórios
- Decisões arquiteturais
- Estratégia de testes
Passo 2: Decompor em tasks atômicas
Cada task deve:
- Ser pequena o suficiente para uma conversa única (15–60 min de trabalho)
- Ter dependências reais e mínimas (não falsas)
- Ser testável isoladamente
- Incluir validações de segurança apropriadas
- Ter
complexityhonesta (LOW/MED/HIGH)
Passo 3: Gerar DARE/TASKS.md (visão humana)
# Tasks: [Nome do Projeto]
## Visão Geral
- Total de Tasks: [N]
- Ranks paralelos: [N]
- Tempo estimado: [horas]
## Tabela de Status
| ID | Título | Status | Depends On | Complexity |
|----------|-----------------------------|-------------|------------------|------------|
| task-001 | Setup project structure | ⏳ PENDING | — | LOW |
| task-002 | DB migrations | ⏳ PENDING | — | MED |
| task-003 | Auth controllers | ⏳ PENDING | task-001, 002 | HIGH |
| ... | ... | ... | ... | ... |
## Tarefas por Fase
### Phase 1: Setup
- task-001: Setup project structure
- task-002: DB migrations
### Phase 2: Auth
- task-003: Auth controllers (deps: 001, 002)
- ...
## Próximas Etapas
1. Revisar e aprovar este TASKS.md
2. Executar paralelo: `dare execute --parallel`
3. Ou task isolada: `/dare-execute task-001`
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 · 266 lines · 76 tokens per session scan A b0de7fedb434
dare-tasks is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 2,626 once invoked, about $0.0003 per session on Opus 5.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
writing-skills
Use when creating a new skill for the Shipworthy plugin, or when a recurring failure mode needs to be codified into a reusable guide. Covers TDD-for-documentation, CSO (Claude Search Optimization), adversarial testing, and the full skill lifecycle.
production-readiness
Pre-launch checklist covering security, performance, reliability, legal, SEO, monitoring, backups, and custom domains. Each item has both a plain-language explanation and technical implementation detail. Ensures nothing critical is missed before going live.
compliance-awareness
Practical engineering guidance for SOC 2, GDPR, HIPAA compliance and data classification. Covers access controls, audit logging, change management, right to deletion, data portability, consent, PHI encryption, and data classification levels. Engineering checks, not legal advice.
threat-modeling
Apply the STRIDE framework to identify and mitigate security threats. Covers Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege with practical questions, verification steps, and mitigations for each threat category.
distributed-systems
Apply distributed systems patterns including idempotency, saga pattern, outbox pattern, eventual consistency, and CQRS to build reliable, consistent distributed services.
twelve-factor-app
Evaluate and apply the Twelve-Factor App methodology with modern 2025 interpretations. Covers all 12 factors with actionable checks for cloud-native applications running on containers, Kubernetes, and serverless platforms.