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/brightredchilli/terraform-docs/agents-mdgit clone --depth 1 https://github.com/brightredchilli/terraform-docsWhat 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.00772 | $0.00772 |
| Opus 5 | $0.00386 | $0.00386 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
terraform-docs 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 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repository
Hybrid (BM25 + vector) search over the Terraform AWS and Google provider documentation, exposed as an MCP server and a Python library. The installed artifact is meant to be self-contained and offline: the wheel ships the search index and documentation alongside the code.
Before calling any edit done
Run the type checker — this repo has a pyrightconfig.json
(typeCheckingMode: standard, reportArgumentType: error). Fix what it
reports rather than silencing it.
make typecheck # uv run basedpyright src tests
make check # typecheck + tests
Style
Prefer """ triple-quoted strings over adjacent-literal concatenation for
multiline text ("line one\n" "line two\n" → """line one\nline two""").
This matters most for expected-value fixtures in tests — concatenation is easy
to get subtly wrong (a missing space between fragments, mismatched embedded
quotes) and harder to eyeball against the real content it is meant to match.
Two entry points
cli.py is what gets installed and exposed to users (terraform-docs-mcp
on $PATH): search/get/stats for the command line, and serve to run
the MCP server (stdio or Streamable HTTP). This is the only thing an installed
user ever runs.
build_index.py is development-only, never installed. It builds
_data/ (the packaged search index) and src/summaries/ (per-document
summaries, checked into git as source, not generated at install time). Bare
invocation builds both, skipping whichever hasn't changed:
uv run src/terraform_docs_mcp/build_index.py # everything
uv run src/terraform_docs_mcp/build_index.py index # just the index
uv run src/terraform_docs_mcp/build_index.py summaries # just the summaries
Its imports are absolute (terraform_docs_mcp.x), not relative, specifically
so it can run by path as shown above, not just via -m — a relative import
breaks the moment a file executes as __main__. This is the one module in the
package where that matters; everywhere else, relative imports are the norm.
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 · 74 lines · 772 tokens per session scan A 233433bb8d7c
terraform-docs AGENTS.md is an instructions file published in the GitHub repository brightredchilli/terraform-docs (0 stars, last pushed 20d ago), licensed MPL-2.0. It adds 772 tokens to every session, about $0.0039 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
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.