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/tripplemay/aigcgateway/agents-mdgit clone --depth 1 https://github.com/tripplemay/aigcgatewayWrote 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/tripplemay/aigcgateway/agents-md)<a href="https://agentmods.dev/instructions/tripplemay/aigcgateway/agents-md"><img src="https://agentmods.dev/badge/instructions/tripplemay/aigcgateway/agents-md.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.01072 | $0.01072 |
| Opus 5 | $0.00536 | $0.00536 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
aigcgateway AGENTS.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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 105 lines · 1,072 tokens per session scan A 25b89c2e2ef3
aigcgateway AGENTS.md is an instructions file published in the GitHub repository tripplemay/aigcgateway (2 stars, last pushed 28d ago), with no licence file. It adds 1,072 tokens to every session, about $0.0054 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 instructions, from other repositories
dbt-mcp CLAUDE.md
Claude Code instructions for dbt-labs/dbt-mcp, covering claude.md, project overview, key paths, tool architecture and mcp apps (tools with interactive ui).
dbt-mcp AGENTS.md
AGENTS.md instructions for dbt-labs/dbt-mcp: See CLAUDE.md for additional context and instructions.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
unraid CLAUDE.md
Claude Code instructions for dinglebear-ai/unraid, covering claude.md, what this is, identity and history (read before touching any url), "unraid-mcp" means five different things and agent plugins ship no claude code hooks.
pfsense-mcp-server AGENTS.md
AGENTS.md instructions for night4me/pfsense-mcp-server, covering pfsense mcp server, architecture and security, development workflow, long-running validation and test parallelism.
swag-mcp CLAUDE.md
Claude Code instructions for jmagar/swag-mcp, covering swag mcp - claude memory reference, project overview, core architecture, key components and common development commands.