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 instructions/hecatehq/hecate/providersgit clone --depth 1 https://github.com/hecatehq/hecateWrote 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/instructions/hecatehq/hecate/providers)<a href="https://agentmods.dev/instructions/hecatehq/hecate/providers"><img src="https://agentmods.dev/badge/instructions/hecatehq/hecate/providers.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.00179 | $0.00179 |
| Opus 5 | $0.00089 | $0.00089 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
hecate providers.instructions.md 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.
What it actually says
Provider Boundary
For provider work, read internal/providers/AGENTS.md and
docs-ai/skills/providers/SKILL.md before editing.
High-signal rules:
- The API-side uppercase structs and provider-side lowercase structs are intentionally duplicated. Do not unify them.
- When adding a passthrough field, mirror the full chain across public types,
API structs, provider structs, both
ChatandChatStream, and tests. - Translate or explicitly drop unsupported cross-provider fields.
- Seed capability caches in provider tests when discovery is not the behavior under test.
- Streaming paths need dedicated tests; non-stream tests do not prove streaming wire plumbing works.
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 · 21 lines · 179 tokens per session scan A 02fb835687b6
hecate providers.instructions.md is an instructions file published in the GitHub repository hecatehq/hecate (22 stars, last pushed 2d ago), licensed MIT. It adds 179 tokens to every session, about $0.0009 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-30.
Other instructions, from other repositories
bifrost AGENTS.md
AGENTS.md instructions for maximhq/bifrost, covering agents.md — bifrost ai gateway, what is bifrost?, repository layout, go workspace and build, test & dev commands.
studio AGENTS.md
AGENTS.md instructions for decocms/studio, covering repository guidelines, documentation philosophy, commands, development and start full dev environment (migrations + client + server).
ai-gateway AGENTS.md
AGENTS.md instructions for ferro-labs/ai-gateway, covering agents.md, project overview, current development snapshot, public-facing wording and build, test, and run commands.
litellm AGENTS.md
AGENTS.md instructions for BerriAI/litellm, a project described as: The fastest, litest AI Gateway. Rust core with Python SDK. Call 100+ LLM APIs in OpenAI (or native) format with cost tracking, guardrails, load balancing, and logging [Bedrock, Azure, OpenAI, Anthropic, OpenAI, VertexAI, vLLM, Nvidia NIM].
litellm GEMINI.md
Gemini CLI instructions for BerriAI/litellm, a project described as: The fastest, litest AI Gateway. Rust core with Python SDK. Call 100+ LLM APIs in OpenAI (or native) format with cost tracking, guardrails, load balancing, and logging [Bedrock, Azure, OpenAI, Anthropic, OpenAI, VertexAI, vLLM, Nvidia NIM].
zypher-agent CLAUDE.md
Instructions for corespeed-io/zypher-agent, covering claude.md, development commands, code quality, architecture overview and monorepo structure.