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-telemetry)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-telemetry"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-telemetry/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-telemetry"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-telemetry.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.01039 |
| Opus 5.5 | $0.00000 | $0.00416 |
| Sonnet 5.5 | $0.00000 | $0.00208 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
dare-telemetry 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-telemetry
Rastreia tokens e modelos de IA usados em cada etapa do Método DARE. Atualiza DARE/TELEMETRY.md com modelo, tokens, tempo e tentativas (Ralph Loop) por comando.
Como usar
/dare-telemetry # gera relatório completo
/dare-telemetry append <comando> # adiciona entrada do último comando
/dare-telemetry report # gera resumo + custo estimado
Diferença com /dare-quality-telemetry
/dare-telemetry— uso de IA (modelos, tokens, tempo)/dare-quality-telemetry— métricas de qualidade das skills (M-01 a M-04)
Modelos rastreáveis
| Modelo | Provider | Melhor para |
|---|---|---|
| Claude Opus 4.7 | Anthropic | Design, blueprint, security review |
| Claude Sonnet 4.5 | Anthropic | Execução de tasks |
| GPT-4 Turbo | OpenAI | Tarefas gerais |
| Gemini 2.0 Flash | Tasks simples, batch | |
| Ollama (local) | Self-hosted | Dados sensíveis |
Estrutura DARE/TELEMETRY.md
# Telemetria do Projeto
## Resumo Executivo
- Projeto: [Nome]
- Tokens totais: 147,909 in / 38,250 out
- Modelos: Opus 4.7, Sonnet 4.5
- Tempo total: ~31 min
- Custo estimado: $2.63
## Detalhamento por Etapa
### 1. Design
- Timestamp, Modelo, Tokens in/out, Tempo, Comando, Resultado
### 2. Blueprint
- (idem)
### 3. Tasks
- (idem) + número de tasks geradas
### 4. Execute Tasks
Por task:
- task-001 — Migration
- Modelo, Tokens, Tempo
- Tentativas Ralph Loop: 1
- Status: ✓
## Análise
| Etapa | Tokens in/out | % | Tempo |
|---|---|---|---|
## Custo estimado
| Modelo | In | Out | $/M in | $/M out | Total |
|---|---|---|---|---|---|
O que fazer
Passo 1: Após cada comando DARE
Adicione entrada com:
- Timestamp (
date -u +%FT%TZ) - Modelo do agente
- Tokens estimados in/out (pegar do output se disponível, perguntar se não)
- Tempo de execução
- Comando exato executado
- Resultado (arquivo gerado, número de tasks, etc.)
- Observações qualitativas
Passo 2: Para /dare-execute de cada task
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 · 133 lines · 0 tokens per session scan A 1d745e2c7cd3
dare-telemetry 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 1,039 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
context
Command "context" from Vimalk0703/shipworthy, covering process, 1. context infrastructure, 2. regression fence health, 3. session signals and 4. context completeness.
diagnose
Command "diagnose" from Vimalk0703/shipworthy, covering process, example output, project diagnosis report, critical (fix immediately) and high (fix soon).
health
Command "health" from Vimalk0703/shipworthy, covering part 1: plugin installation health and part 2: project health.
validate
Command "validate" from Vimalk0703/shipworthy, covering /validate — pre-push validation gate, what this does, steps, when to run and output format.
retro
Command "retro" from Vimalk0703/shipworthy, covering process and important.
audit
Before executing this command, output.