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-dag-run)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-dag-run"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-dag-run/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-dag-run"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-dag-run.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.00838 |
| Opus 5.5 | $0.00000 | $0.00335 |
| Sonnet 5.5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
dare-dag-run 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dare-dag-run — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-dag-run
Executa o grafo de tasks definido em DARE/dare-dag.yaml usando Claude
Code como executor e o CLI dare como orquestrador. O canvas ao vivo fica
em DARE/.canvas.md.
Sem API keys. Você (Claude Code) usa o plano da IDE/CLI em que o usuário já está autenticado. O CLI apenas coordena estado, monta prompts e atualiza canvas.
Pré-requisitos
DARE/dare-dag.yamlexiste e foi aprovado- Specs em
DARE/EXECUTION/task-<id>.mdgeradas daredisponível no PATH (npm i -g @dewtech/dare-cli)
Como usar
/dare-dag-run
/dare-dag-run --task task-003 # executar só uma task específica
O que fazer
1. Validar pré-condições
- Confirme que
DARE/dare-dag.yamlexiste. Se não, oriente/dare-blueprintou/dare-dag-build - Leia o YAML e verifique sem ciclos, ids únicos, ranks paralelizáveis
2. Pegar próximas tasks
dare execute --next
O CLI imprime as tasks ready do rank atual com o prompt completo (snippets de até 2000 chars dos outputs dos pais já costurados). Use esses prompts.
3. Sugerir abrir o canvas
Antes de começar, peça ao usuário abrir DARE/.canvas.md em outra aba.
4. Executar cada task
Para cada task ready:
- Leia
spec_filese houver - Implemente conforme o prompt
- Rode Ralph Loop: build → test → lint
- Registre o resultado:
# Sucesso
dare execute --complete task-001 --output "Resumo + arquivos criados (paths)"
# Falha
dare execute --fail task-002 --reason "Mensagem clara da falha"
5. Avançar de rank
dare execute --next
Se aparece ✅ All tasks resolved, todas terminaram. Caso contrário, continue.
6. Pós-execução
dare execute --status
Para retentar tasks FAILED:
dare execute --reset task-002
dare execute --next
Comandos do orquestrador
| Comando | Função |
|---|---|
dare execute --next |
Próximas tasks ready com prompts compostos |
dare execute --complete <id> --output "…" |
Marca DONE |
dare execute --fail <id> --reason "…" |
Marca FAILED + cascade-skip |
dare execute --reset <id> |
Volta para PENDING |
dare execute --status |
Snapshot do canvas + sumário |
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.
- 2mo ago First seen · 110 lines · 0 tokens per session scan A 684994e04c39
dare-dag-run is a command published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 838 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-08-31.
dare-dag-run compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dare-dag-rundewtech-technologies/dare-method | Command | 5 | 4mo ago | MIT | A | 0 | Claude Code |
| contextVimalk0703/shipworthy | Command | 6 | 7mo ago | MIT | A | 0 | Claude Code |
| diagnoseVimalk0703/shipworthy | Command | 6 | 7mo ago | MIT | A | 0 | Claude Code |
| healthVimalk0703/shipworthy | Command | 6 | 7mo ago | MIT | A | 0 | Claude Code |
| retroVimalk0703/shipworthy | Command | 6 | 7mo ago | MIT | A | 0 | Claude Code |
| validateVimalk0703/shipworthy | Command | 6 | 7mo ago | MIT | A | 0 | Claude Code |
| auditVimalk0703/shipworthy | Command | 6 | 7mo ago | MIT | A | 0 | Claude Code |