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 agentmods add skills/dewtech-technologies/dare-method/dare-llm-integrationnpx skills add dewtech-technologies/dare-method --skill dare-llm-integrationgit 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-llm-integration)<a href="https://agentmods.dev/skills/dewtech-technologies/dare-method/dare-llm-integration"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/dare-llm-integration.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 | $0.00076 | $0.01811 |
| Opus 5 | $0.00038 | $0.00905 |
| Sonnet 5 | $0.00015 | $0.00362 |
| Haiku 4.5 | $0.00008 | $0.00181 |
Grade A, and why
dare-llm-integration 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 4d 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 LLM Integration Skill
Você é um especialista em integração com LLMs (Gemini, Claude, GPT, modelos locais). Seu papel é garantir que toda chamada a LLM em projeto DARE seja abstraída, cacheada, rate-limited, validada e auditável.
Quando usar esta skill
- Projeto vai consumir Gemini, Claude API, OpenAI, Ollama ou similar
- Você está revisando Handler que chama SDK de LLM diretamente
- Você está auditando custos de LLM no projeto
- Você está adicionando proteção contra prompt injection
A arquitetura recomendada
┌────────────────────────────────────────────────────────┐
│ Handler / Service │
└────────────────────────────────────────────────────────┘
↓ injeta
┌────────────────────────────────────────────────────────┐
│ LLMProvider (interface) │
│ ├── GeminiProvider │
│ ├── ClaudeProvider │
│ ├── OpenAIProvider │
│ └── OllamaProvider (local) │
└────────────────────────────────────────────────────────┘
↓ wrapping
┌────────────────────────────────────────────────────────┐
│ Cache (TTL) + RateLimit (token bucket) + Schema │
└────────────────────────────────────────────────────────┘
↓
┌────────────────────────────────────────────────────────┐
│ HTTP call externo (Gemini API, etc.) │
└────────────────────────────────────────────────────────┘
Os 5 pilares
1. LLMProvider abstraction
NUNCA chame SDK do Gemini/OpenAI dentro de um Handler ou Service de negócio. Sempre passe pela interface LLMProvider.
// ❌ Errado
class SummaryService {
async run(text: string) {
const client = new GoogleGenAI({apiKey: 'xxx'});
return client.generateContent({contents: text});
}
}
// ✅ Certo
class SummaryService {
constructor(private llm: LLMProvider) {}
async run(text: string) {
return this.llm.complete({
promptId: 'summarize-v1',
input: { text },
schema: SummarySchema,
});
}
}
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.
- 4d ago First seen · 218 lines · 76 tokens per session scan A a8037a29384b
dare-llm-integration is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,811 once invoked, about $0.0004 per session on Opus 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
openai-agents-guide
Guide to building AI agents with the OpenAI Agents SDK covering agent creation, tool use, context management, guardrails, handoffs, multi-agent orchestration, and tracing.
inbound-triage
Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the…
setup-background-job
Set up scheduled background jobs using Quartz.NET with proper configuration, error handling, and dependency injection.
conventional-commits
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…
pr-writing
Use whenever writing a PR title/description, a commit message body, a code review comment, or an issue — in Hedgehog's own repo or any consuming project. Triggers on "open a PR", "write the PR description", "comment on this PR", "file an issue". Covers writing style (terse, info-dense, Simplified Technical English)…
prompt-sensei
Stage-aware prompt coaching, prompt improvement, lookback analysis, prompting habit feedback, and local reports about prompt quality for AI coding agents such as Claude Code or Codex.