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-validate)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-validate"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-validate/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-validate"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-validate.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.00227 |
| Opus 5.5 | $0.00000 | $0.00091 |
| Sonnet 5.5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
dare-validate 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.
What it actually says
/dare-validate
Valida DARE/dare-dag.yaml (ciclos, referências quebradas, campos obrigatórios). Adequado para pre-commit hooks e CI.
Este comando expõe o CLI
dare validatena IDE. O agente pode rodar o comando no terminal e interpretar a saída.
Quando usar
- Antes de commitar mudanças no DAG.
- Em CI, como gate de integridade do plano de execução.
Como rodar
dare validate
dare validate --strict # trata warnings como erros (CI-friendly)
dare validate --dag DARE/dare-dag.yaml
O que fazer
- Rode
dare validate(use--strictem CI). - Se houver erros, corrija o
dare-dag.yamlapontado e rode de novo até passar. - Saída limpa = DAG íntegro e pronto para
/dare-execute.
Comandos relacionados
/dare-dag · /dare-execute
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 · 29 lines · 0 tokens per session scan A 8687912539ab
dare-validate 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 227 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.