Borrowing it
Nothing to install: this file belongs to berkayildi/mcp-tfstate-reader. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/berkayildi/mcp-tfstate-reader/main/CLAUDE.mdgit clone --depth 1 https://github.com/berkayildi/mcp-tfstate-readerWrote 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/berkayildi/mcp-tfstate-reader/claude-md)<a href="https://agentmods.dev/instructions/berkayildi/mcp-tfstate-reader/claude-md"><img src="https://agentmods.dev/badge/instructions/berkayildi/mcp-tfstate-reader/claude-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.01175 | $0.01175 |
| Opus 5 | $0.00588 | $0.00588 |
| Sonnet 5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
mcp-tfstate-reader CLAUDE.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 6d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — mcp-tfstate-reader
This file helps Claude Code understand the project structure and conventions for future sessions.
Project overview
mcp-tfstate-reader is a local MCP (Model Context Protocol) server written in Python. It parses Terraform .tfstate files and exposes five tools that allow AI agents to audit infrastructure for security misconfigurations without needing live cloud credentials.
Transport: stdio (standard input/output).
Directory structure
mcp-tfstate-reader/
├── src/
│ └── mcp_tfstate_reader/
│ ├── __init__.py # Package version
│ └── server.py # All MCP tool logic (single file)
├── tests/
│ ├── __init__.py
│ ├── fixtures/
│ │ └── sample.tfstate # Comprehensive fixture covering all audit rules
│ └── test_server.py # pytest tests — imports internals directly
├── pyproject.toml # Build config (hatchling), deps, pytest settings
├── Makefile # setup / build / start / test / clean
├── README.md # User-facing docs with MCP config examples
├── CLAUDE.md # This file
└── .gitignore
Key design decisions
-
Single-file server — all tool logic lives in
src/mcp_tfstate_reader/server.py. Keep it that way unless the file exceeds ~500 lines. -
No external dependencies beyond
mcpSDK for runtime, andpytest+pytest-asynciofor tests. Do not addboto3,pydantic, or other libraries without a strong reason. -
Private helpers are directly importable in tests — the test file imports
_load_tfstate,_iter_resources,_list_resources,_audit_security,_get_resource_detail,_summarize_state, and_compare_statesdirectly. Keep these functions at module level. -
asyncio_mode = "auto"is set inpyproject.toml, so@pytest.mark.asynciois optional but harmless to include. -
Resource address format follows Terraform convention:
<type>.<name>for root module,<module>.<type>.<name>for nested modules. Index suffixes ([0],["key"]) are appended for multi-instance resources.
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.
- 6d ago First seen · 107 lines · 1,175 tokens per session scan A 0a208d9f39af
mcp-tfstate-reader CLAUDE.md is an instructions file published in the GitHub repository berkayildi/mcp-tfstate-reader (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,175 tokens to every session, about $0.0059 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
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.