mcpcodeanalysis: Instructions file for Codex

AGENTS.md

mcpcodeanalysis AGENTS.md is an instructions file for Codex, OpenCode from johannhartmann/mcpcodeanalysis. It costs 689 tokens per session, scanned A, original, MIT.

Repository instructions for contributing to an MCP code-analysis server written in Python. Repository instructions are project-specific rules for organizing code, running commands, and writing tests.

In plain words
What is it for?
Use them when installing dependencies, running the server, checking or formatting Python code, and running unit or integration tests.
Why use it?
They provide the expected project layout, coding standards, development commands, and testing process in one place.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is johannhartmann/mcpcodeanalysis's own configuration. It tells Codex and OpenCode how to work on mcpcodeanalysis itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcpcodeanalysis configures →

Reuse

Borrowing it

Nothing to install: this file belongs to johannhartmann/mcpcodeanalysis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/johannhartmann/mcpcodeanalysis/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/johannhartmann/mcpcodeanalysis

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for mcpcodeanalysis AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/johannhartmann/mcpcodeanalysis/agents-md/github.svg)](https://agentmods.dev/instructions/johannhartmann/mcpcodeanalysis/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/johannhartmann/mcpcodeanalysis/agents-md"><img src="https://agentmods.dev/badge/instructions/johannhartmann/mcpcodeanalysis/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcpcodeanalysis AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/johannhartmann/mcpcodeanalysis/agents-md"><img src="https://agentmods.dev/badge/instructions/johannhartmann/mcpcodeanalysis/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 689 This file is loaded in full into every session.
When invoked 689 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00689 $0.00689
Opus 5.5 $0.00276 $0.00276
Sonnet 5.5 $0.00138 $0.00138
Haiku 4.5 $0.00069 $0.00069

Measured 2mo ago against content hash 14338d7e84e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

AGENTS.md · 38 lines

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/: Mirrors src/ by area with test_*.py files; includes unit/, integration/, and feature folders.
  • docs/, alembic.ini, docker-compose.yml, config.example.yaml, settings.toml support 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) or make 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-server or uv 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_case for functions/vars, PascalCase classes, lower_snake_case.py modules, package dirs lowercase.

Testing Guidelines

  • Framework: pytest with 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 via make 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 qa passes locally.

Read the full file on GitHub · 38 lines

Changes

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.

  1. 2mo ago First seen · 38 lines · 689 tokens per session scan A 14338d7e84e6

Subscribe to this mod's changes

mcpcodeanalysis AGENTS.md is an instructions file published in the GitHub repository johannhartmann/mcpcodeanalysis (10 stars, last pushed 1y ago), licensed MIT. It adds 689 tokens to every session, about $0.0028 per session on Opus 5.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.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens