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-bench)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-bench"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-bench/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-bench"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-bench.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.00152 |
| Opus 5.5 | $0.00000 | $0.00061 |
| Sonnet 5.5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
dare-bench 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-bench
Roda o harness determinístico de fixtures de verificação (dare bench) — mede Fix·Rate e solve-rate contra patches versionados.
Este comando expõe o CLI
dare benchna IDE.
Como rodar
dare bench --suite fixtures/bench --json
dare bench --suite fixtures/bench --baseline bench-baseline.json --fail-on-regression 3
O que fazer
- Rode
dare benchcom--jsonpara relatório estruturado. - Compare com
--baselineem CI; exit 1 = regressão > limiar pp. - Exit 2 = suite inválida/ausente.
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 · 19 lines · 0 tokens per session scan A b49f1ef764eb
dare-bench 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 152 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.
Other commands, from other repositories
validate
Command "validate" from Vimalk0703/shipworthy, covering /validate — pre-push validation gate, what this does, steps, when to run and output format.
deps-update
Audit and update dependencies safely.
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
ccc-feature-start
Kick off a feature: research context, create an isolated branch, confirm a green baseline, write a task breakdown, and the first failing test. Use when starting new feature work in a git repository.
test-gen
Generate comprehensive tests for a specified file with edge cases and error scenarios.