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.
npx skills add dewtech-technologies/dare-method --skill dare-realtimegit 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/skills/dewtech-technologies/dare-method/dare-realtime)<a href="https://agentmods.dev/skills/dewtech-technologies/dare-method/dare-realtime"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/dare-realtime/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/skills/dewtech-technologies/dare-method/dare-realtime"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/dare-realtime.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.00054 | $0.01853 |
| Opus 5.5 | $0.00022 | $0.00741 |
| Sonnet 5.5 | $0.00011 | $0.00371 |
| Haiku 4.5 | $0.00005 | $0.00185 |
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 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DARE Realtime Skill
Você é um especialista em comunicação real-time. Seu papel é garantir que toda integração WebSocket/SSE em projeto DARE seja tipada, autorizada, reconectável e sem ghost listeners.
Quando usar esta skill
- Projeto precisa de WebSocket (chat, notifications, live updates)
- Projeto precisa de SSE (logs streaming, métricas em tempo real)
- Você está auditando ghost listeners (memória crescendo após desconexão)
- Você está revisando código que faz
socket.on('event', ...)sem cleanup
Arquitetura recomendada
┌─────────────────────────────────────────────────────────┐
│ Event Registry │
│ - Tipos de evento com schema JSON │
│ - Versionamento (v1, v2…) │
│ - Autorização por evento │
└─────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────┐
│ Subscription Manager │
│ - Map<connection_id, Set<event_type>> │
│ - Cleanup garantido on disconnect │
└─────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────┐
│ Reconnect Strategy │
│ - Exponential backoff (1s, 2s, 4s, 8s, max 30s) │
│ - Jitter para evitar thundering herd │
│ - Resync de estado após reconectar │
└─────────────────────────────────────────────────────────┘
Os 4 pilares
1. Schema validation de eventos
Todo evento WebSocket/SSE tem schema JSON:
// event_registry.ts
const events = {
'user.created.v1': z.object({
id: z.string().uuid(),
email: z.string().email(),
createdAt: z.string().datetime(),
}),
'message.sent.v1': z.object({
conversationId: z.string().uuid(),
senderId: z.string().uuid(),
body: z.string().max(2000),
sentAt: z.string().datetime(),
}),
};
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 · 218 lines · 54 tokens per session scan A e060ed137260
dare-realtime is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 1,853 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
distributed-systems
Apply distributed systems patterns including idempotency, saga pattern, outbox pattern, eventual consistency, and CQRS to build reliable, consistent distributed services.
resilience-patterns
Apply resilience patterns (circuit breakers, bulkheads, retries, timeouts, graceful degradation, DLQs) to distributed services to prevent cascading failures and maintain availability under partial outages.
api-backward-compatibility
Design and evolve APIs without breaking existing consumers. Covers additive-only changes, versioning strategies, deprecation workflows, consumer-driven contract testing, and backward-compatible defaults. References Stripe's API stability as the gold standard.
response-schema-validation
Use when building APIs to enforce that every response matches a declared schema before reaching the client. Prevents accidental data leakage, field mismatches, and contract violations.
api-versioning
Breaking change detection, versioning strategies (URL path vs header), deprecation policies, backward compatibility rules, and OpenAPI spec maintenance.
observability-by-default
Structured logging, request tracing, health checks, error tracking, and key metrics. Every service should be observable from day one.