MCPAudit AGENTS.md

A project instruction file for MCPAudit, a local tool that checks Model Context Protocol configurations and reports what connected servers may access.

In plain words
What is it for?
Use it when developing or operating MCPAudit, running tests and linting, performing configuration audits, or producing scan reports.
Why use it?
It defines the project's safe, read-only operating rules, current state, technology stack, and recommended checks.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/saagpatel/mcpaudit/agents-md
Clone the repo
git clone --depth 1 https://github.com/saagpatel/MCPAudit

Made for: Codex, OpenCode.

Per session 802 This file is loaded in full into every session.
When invoked 802 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00802 $0.00802
Opus 5 $0.00401 $0.00401
Sonnet 5 $0.00160 $0.00160
Haiku 4.5 $0.00080 $0.00080

Measured 2d ago against content hash d0d7a7994720, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

What This Project Is

MCPAudit is a local MCP security and drift audit tool. It inspects MCP client/server configuration and reports what configured servers can reach, with read-only safety as the default operating posture.

Current State

The repo is an active infrastructure/security project with package metadata, tests, CI, release docs, and a README that emphasizes zero-touch and read-only scan modes.

Stack

  • Python
  • uv
  • pytest
  • ruff
  • GitHub Actions / CodeQL
  • SARIF/JSON/HTML style reporting surfaces

How To Run

Prefer zero-touch or read-only checks first:

uv run pytest -q
uv run ruff check .
uv run mcp-audit scan --skip-connect

Only run connected scans when the task explicitly calls for live MCP tool-schema inspection and the boundary is clear.

Known Risks

  • MCP config auditing can expose sensitive config shape. Report environment variable key names only, never values.
  • Do not read .env files, keychains, OAuth stores, browser profiles, raw logs, private transcripts, cookies, or credential-bearing configs.
  • Treat remote package verification, downloads, LLM analysis, and connected server scans as higher-reach modes that need explicit justification.

Review guidelines

Focus Codex review on scan correctness, silent skipped checks, degraded-state warnings, report schema compatibility, secret exposure in findings/warnings, and release or registry drift. Treat comments on missing tests as merge-relevant when the change touches detectors, report fields, scan modes, package verification, SARIF/JSON/HTML output, or MCP connection behavior.

For docs-only PRs, comment only when the docs claim a scan, safety property, output field, release version, or verification path that is not supported by the reviewed tree.

Contributing

See CONTRIBUTING.md for the full contribution guide. Before opening a PR:

  • Run uv run pytest -q and confirm all tests pass.
  • Run uv run ruff check . and uv run ruff format --check (zero findings expected).
  • For new detectors or report fields, add fixture-backed tests and update docs/OUTPUT-CONTRACT.md.
  • Prefer config-only (--skip-connect) fixtures; connected fixtures require explicit justification.

Read the full file on GitHub · 102 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. 2d ago First seen · 102 lines · 802 tokens per session scan A d0d7a7994720

Subscribe to this mod's changes

MCPAudit AGENTS.md is an instructions file published in the GitHub repository saagpatel/MCPAudit (4 stars, last pushed 2d ago), licensed MIT. It adds 802 tokens to every session, about $0.0040 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.