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/johannhartmann/mcpcodeanalysis/agents-mdgit clone --depth 1 https://github.com/johannhartmann/mcpcodeanalysisWhat 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.00689 | $0.00689 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
mcpcodeanalysis 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/: Python package with core modules —mcp_server/(MCP server),scanner/,parser/,query/,embeddings/,database/,domain/,indexer/,utils/.tests/: Mirrorssrc/by area withtest_*.pyfiles; includesunit/,integration/, and feature folders.docs/,alembic.ini,docker-compose.yml,config.example.yaml,settings.tomlsupport docs, DB migrations, and config.- Entry points (installed via
uv):mcp-code-server,mcp-scanner,mcp-indexer.
Build, Test, and Development Commands
- Install deps:
make dev-install(dev + pre-commit) ormake install(prod only). - Lint/format/type-check:
make lint,make format,make type-check, full QA:make qa. - Run tests:
make test(unit),make test-integration,make test-all, coverage HTML:make coverage-html. - Quick feedback loop (Just):
just unveil-next-error,just see-what-you-did-there. - Run locally:
uv run mcp-code-serveroruv run python -m src.mcp_server.
Coding Style & Naming Conventions
- Python 3.11+, Black (88 cols), Ruff, isort; 4-space indents.
- Type hints required in code paths (mypy strict settings); prefer explicit return types.
- Imports: prefer absolute; relative imports are lint-banned.
- Naming:
snake_casefor functions/vars,PascalCaseclasses,lower_snake_case.pymodules, package dirs lowercase.
Testing Guidelines
- Framework:
pytestwith markers:unit,integration,slow,requires_db,requires_openai. - Structure:
tests/<area>/test_*.py; keep tests close to the feature area. - Run examples:
uv run pytest -m "unit" -q,uv run pytest -m "integration" -v. - Coverage is preconfigured (
--cov=src); open report viamake coverage-html.
Commit & Pull Request Guidelines
- Use Conventional Commits: e.g.,
feat: …,fix: …,docs: …,refactor: …,ci: …,chore: …. - Scope when helpful:
fix(scanner): handle rate limit. - PRs: follow
.github/pull_request_template.md— clear description, linked issue (Fixes #123), tests, and any screenshots where relevant. - Keep changes focused and ensure
make qapasses locally.
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 · 38 lines · 689 tokens per session scan A 14338d7e84e6
mcpcodeanalysis AGENTS.md is an instructions file published in the GitHub repository johannhartmann/mcpcodeanalysis (11 stars, last pushed 10mo ago), licensed MIT. It adds 689 tokens to every session, about $0.0034 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.
buildNext
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
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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
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.
langchain 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.