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/agents-mdgit 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/agents-md)<a href="https://agentmods.dev/instructions/opsmill/infrahub-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/opsmill/infrahub-mcp/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.1 | $0.01109 | $0.01109 |
| Opus 5 | $0.00554 | $0.00554 |
| Sonnet 5 | $0.00222 | $0.00222 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
infrahub-mcp 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 2d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrahub MCP Server
Connects AI assistants to Infrahub over the open MCP standard, so agents can read and (optionally) change infrastructure state through a consistent, audited, human-approved interface.
Tech Stack
- Runtime: Python 3.13, FastMCP, Infrahub SDK, Pydantic 2, Starlette
- Testing: pytest, pytest-asyncio
- Linting: ruff, mypy, pylint, yamllint
- Docs: Docusaurus (
.mdxindocs/docs/), rumdl for markdown linting - Package Manager: uv
File Structure
src/infrahub_mcp/— Library source codetools/— MCP tool implementations (gql, nodes, schema, session, write)resources/— MCP resources (branches, schema)prompts/— MCP prompt templatesmiddleware.py— Full middleware stack (logging, caching, auth, rate limiting, audit)server.py— FastMCP server construction and ASGI appconfig.py—ServerConfigvia pydantic-settingsauth.py— OIDC provider factory and identity helpers
tests/— Test suitedocs/— User-facing documentation (Docusaurus)dev/— Internal developer documentation — see dev/README.md.agents/— AI agent commands and skills.specify/— Speckit scaffolding (templates, workflows, extensions)
Commands
uv sync # Install dependencies
uv run pytest # Run full test suite
uv run invoke format # Auto-format with ruff
uv run invoke lint # All linters (yaml, ruff, pylint, mypy)
uv run invoke lint-ruff # Ruff only
uv run invoke lint-pylint # Pylint only
uv run invoke lint-mypy # MyPy type checking only
uv run invoke lint-yaml # Yamllint only
uv run rumdl check docs/docs/ # Check markdown linting
uv run rumdl fmt docs/docs/ # Auto-fix markdown formatting
cd docs && npm run build # Test documentation build
uv run pre-commit run # Ruff + rumdl on staged files, Mypy on src/
uv run pre-commit install # Optional: run those same hooks on every commit
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.
- 2d ago First seen · 103 lines · 1,109 tokens per session scan A c394d7532f73
infrahub-mcp AGENTS.md is an instructions file published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,109 tokens to every session, about $0.0055 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
autolith AGENTS.md
AGENTS.md instructions for lambda-symbolics/autolith, covering repository guidelines, purpose and sources of truth, upstream references, architectural guardrails and package policy.
senpi AGENTS.md
AGENTS.md instructions for code-yeongyu/senpi, covering senpi repository guide, mandatory execution protocols — non-negotiable, protocol 1 — explicitly requested modifications, protocol 2 — user-requested pr reviews and structure.
hoop CLAUDE.md
Claude Code instructions for hoophq/hoop, covering claude.md, project overview, toolchain & prerequisites, architecture and module breakdown.
rome CLAUDE.md
Claude Code instructions for rome-os/rome, covering rome, playbook and traps.
zapcode CLAUDE.md
Instructions for TheUncharted/zapcode, covering claude.md, git, read agents.md first, codebase orientation and how to add a new language feature.
memory-bridge AGENTS.md
AGENTS.md instructions for jiabaobei/memory-bridge, covering agents.md — 记忆桥项目规约(ai 协作会话必读), 版本与发布(硬性规则,所有者 2026-08-29 定), 架构铁律 and 工程习惯.