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/opsmill/infrahub-mcp/toolinggit clone --depth 1 https://github.com/opsmill/infrahub-mcpWrote 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/opsmill/infrahub-mcp/tooling)<a href="https://agentmods.dev/instructions/opsmill/infrahub-mcp/tooling"><img src="https://agentmods.dev/badge/instructions/opsmill/infrahub-mcp/tooling.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.00069 | $0.00069 |
| Opus 5 | $0.00034 | $0.00034 |
| Sonnet 5 | $0.00014 | $0.00014 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
infrahub-mcp tooling.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 yesterday.
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
Tooling rules
- Prefer Github Actions for automated validation when user commit to the repository
- Don't use Git precommit
- Use ruff and mypy to validate and lint python files
- Use yamllint to validate yaml files
- Use uv to manage the python project and its dependencies
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.
- yesterday First seen · 12 lines · 69 tokens per session scan A 46c83d508981
infrahub-mcp tooling.instructions.md is an instructions file published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session, about $0.0003 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-09-03.
Other instructions, from other repositories
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
agentpool copilot-instructions.md
Instructions for phil65/agentpool, covering code style, tests and docstrings.
pipelex CLAUDE.md
Claude Code instructions for Pipelex/pipelex, covering pipelex coding rules, commands, linting, keyword-only arguments check and cleaning derived files.
dingo AGENTS.md
AGENTS.md instructions for MigoXLab/dingo, covering dingo — agent instructions, project overview, tech stack, directory structure and core concepts.
parlant CLAUDE.md
Instructions for emcie-co/parlant: This is the main repo of Parlant (https://parlant.io).
redis-vl-python CLAUDE.md
Claude Code instructions for redis/redis-vl-python, covering claude.md - redisvl project context, frequently used commands, development workflow, redis setup and documentation.