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-realtime)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-realtime"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-realtime.svg" alt="Measured on agentmods" 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.01163 |
| Opus 5 | $0.00000 | $0.00581 |
| Sonnet 5 | $0.00000 | $0.00233 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
dare-realtime 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 3d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-realtime
Comunicação real-time (WebSocket, SSE) DARE-compliant — eventos tipados, subscriptions autorizadas, reconexão com backoff, zero ghost listeners.
Como usar
/dare-realtime # audita uso de WS/SSE no projeto
/dare-realtime scaffold ws # gera event registry + subscription manager + reconnect
/dare-realtime audit ghosts # detecta listeners sem cleanup
Os 4 pilares
1. Schema validation de eventos
Todo evento WS/SSE tem schema JSON. Server valida antes de emitir, client valida antes de processar.
2. Registro central de tipos
Um único event_registry.ts lista todos os event types com versão (.v1, .v2).
3. Reconexão com exponential backoff
class ReconnectStrategy {
private attempt = 0;
next(): number {
const base = Math.min(1000 * 2 ** this.attempt, 30_000);
return base + Math.random() * 1000; // jitter
}
reset() { this.attempt = 0; }
}
4. Subscription manager (zero ghost listeners)
Map de subscriptions com cleanup automático on disconnect.
Métricas obrigatórias
| ID | Métrica |
|---|---|
| M-01 | 100% de event types com JSON Schema |
| M-02 | 100% de subscriptions autorizadas |
| M-03 | 0 ghost listeners após desconexão |
| M-04 | Estratégia de reconexão configurada |
Antipatterns
| AP | Antipattern | Correção |
|---|---|---|
| AP-01 | Evento sem schema | Adicionar no registry |
| AP-02 | socket.on() sem cleanup |
SubscriptionManager |
| AP-03 | Reconexão sem backoff | Exponential + jitter |
| AP-04 | Sem autorização de subscription | authorize() antes de subscribe() |
| AP-05 | Broadcast sem filtro | Rooms por tenant |
| AP-06 | Estado stale após reconectar | Resync via REST/snapshot |
O que fazer
Passo 1: Event Registry
export const EventRegistry = {
'user.created.v1': { schema: UserCreatedSchema, requires: 'admin' },
'message.sent.v1': { schema: MessageSentSchema, requires: 'participant' },
};
Passo 2: Subscription Manager
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.
- 3d ago First seen · 160 lines · 0 tokens per session scan A 113a46ca92af
dare-realtime is a command published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,163 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
contract-version-bump
Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog entry, downstream drift.
dev-supabase
Configure and use Supabase as a backend (Auth, Database, Storage, Realtime, Edge Functions).
api-gen
Generate REST API endpoints with routes, validation, error handling, and tests.
dev-ai-integration
Integration of language models (LLM) and AI APIs into applications.
dev-api
Create or document REST, GraphQL, or tRPC endpoints, with a versioning strategy.
dev-error-handling
Implements a robust and consistent error handling strategy.