Borrowing it
Nothing to install: this file belongs to SamuelDudley/ism-mcp. 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/SamuelDudley/ism-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/SamuelDudley/ism-mcpWrote 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/samueldudley/ism-mcp/claude-md)<a href="https://agentmods.dev/instructions/samueldudley/ism-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/samueldudley/ism-mcp/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.01447 | $0.01447 |
| Opus 5 | $0.00724 | $0.00724 |
| Sonnet 5 | $0.00289 | $0.00289 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
ism-mcp 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 8d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project guidance for AI agents
Read this before doing any work in this repo. Update it when conventions change.
What this project is
ism-mcp is a local MCP server that exposes the ASD Information Security Manual as queryable tools. It parses the official OSCAL release of the ISM (from the ACSC ism-oscal git mirror) into a version-keyed SQLite database holding the full ISM release history, then serves lookup, version-diff, and coverage tools over stdio. Read README.md for install and usage.
Repository layout
src/ism_mcp/ the package
__init__.py
__main__.py CLI: fetch, ingest, ingest-history, update, serve, install
models.py vocabulary literals + response TypedDicts for the MCP tools
store.py version-keyed SQLite schema + queries + FTS5 + version registry
oscal.py parse an OSCAL ISM catalog into version metadata and control rows
fetch.py clone/pull the ACSC ism-oscal mirror, list tags, read files at a tag
ingest.py orchestrate OSCAL ingest over a directory or a git-tag walk
diff.py catalog delta between two versions + per-control history
retrieve.py cosine search + Reciprocal Rank Fusion
embed.py embedder protocol + fastembed and hash backends
classification.py classification + maturity input normalisation
paths.py repo-path token expansion for query enrichment
coverage.py coverage manifest read, validate, serialise, gaps, drift
install.py consumer-repo install writer
server.py FastMCP server: lookup, discovery, version, coverage tools
data/ path keyword map + coverage template
tests/ pytest suite with hermetic fixtures (tests/fixtures/oscal mini catalogs)
scripts/ci.sh local CI entrypoint
.github/workflows/ci.yml GitHub Actions: runs scripts/ci.sh and the slow suite on every trigger
pyproject.toml uv-managed, hatchling build
glama.json maintainer metadata for the Glama MCP directory
README.md user-facing install and usage
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.
- 8d ago First seen · 126 lines · 1,447 tokens per session scan A 5dd2dfe5baf1
ism-mcp CLAUDE.md is an instructions file published in the GitHub repository SamuelDudley/ism-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,447 tokens to every session, about $0.0072 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
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.
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).
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).
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.
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.