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-tasks)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-tasks"><img src="https://agentmods.dev/badge/commands/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/commands/dewtech-technologies/dare-method/dare-tasks"><img src="https://agentmods.dev/badge/commands/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.00000 | $0.00645 |
| Opus 5.5 | $0.00000 | $0.00258 |
| Sonnet 5.5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-tasks
Exibe o status atual de todas as tasks do projeto e sugere próximos passos.
Como usar
/dare-tasks
/dare-tasks --pending
/dare-tasks --ready
O que fazer
-
Leia os arquivos:
DARE/TASKS.md— status de cada taskDARE/dare-dag.yaml— grafo de dependências
-
Exiba uma tabela formatada:
| ID | Título | Status | Depends On | Complexity | |----------|---------------------------|-------------|------------------|------------| | task-001 | Setup project structure | ✅ DONE | - | LOW | | task-002 | Implement DB schema | 🔄 RUNNING | - | MED | | task-003 | Implement core endpoints | ⏳ PENDING | task-001, 002 | HIGH | -
Destaque tasks prontas para execução:
- Status
PENDINGE todas asdepends_oncom statusDONE - Estas podem ser executadas com
/dare-execute <id>
- Status
-
Calcule e exiba progresso:
- Total de tasks
- Tasks DONE / FAILED / SKIPPED / PENDING / RUNNING
- Percentual concluído
- Barra visual:
█████░░░░░ 50%
-
Identifique gargalos:
- Tasks com mais dependências
- Tasks bloqueando outras
- Tasks no caminho crítico
-
Filtros opcionais:
--pending— só PENDING--ready— só prontas para execução--failed— só FAILED--blocked— PENDING com dependências não satisfeitas
Exemplo de output
📋 DARE Tasks Status
| ID | Título | Status | Depends On |
|----------|---------------------------|-------------|------------------|
| task-001 | Setup project structure | ✅ DONE | - |
| task-002 | Implement DB schema | ✅ DONE | - |
| task-003 | Implement core endpoints | 🟢 READY | task-001, 002 |
| task-004 | Implement auth | 🟢 READY | task-001, 002 |
| task-005 | Write tests | 🔒 BLOCKED | task-003, 004 |
Progress: 2/5 tasks (40%)
████████░░░░░░░░░░░░ 40%
🟢 Ready to execute: task-003, task-004
Run: /dare-execute task-003
Or: dare execute --parallel (executa task-003 e task-004 em paralelo)
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 · 71 lines · 0 tokens per session scan A e781be30d692
dare-tasks is a command 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 645 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
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
handoff
Write a session handoff document for continuity.
update-docs
Scan recently modified files and update the matching documentation.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
status
Show current execution status with progress, dependencies, file ownership, and parallelization opportunities.