Borrowing it
Nothing to install: this file belongs to an0malous/mcp-custos. 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/an0malous/mcp-custos/master/CLAUDE.mdgit clone --depth 1 https://github.com/an0malous/mcp-custosWrote 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/an0malous/mcp-custos/claude-md)<a href="https://agentmods.dev/instructions/an0malous/mcp-custos/claude-md"><img src="https://agentmods.dev/badge/instructions/an0malous/mcp-custos/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.00748 | $0.00748 |
| Opus 5 | $0.00374 | $0.00374 |
| Sonnet 5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
mcp-custos 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 7d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — agent guide
mcp-custos is an MCP server exposing secure-coding and compliance reference data (ISO 27001, NIST 800-53, OWASP ASVS, NIST SSDF, ISO 27017, NIST cloud guidance) plus the pre-edit and pre-commit hooks that make consultation land in code. See README.md for the product picture.
This repo uses Kiro-style spec-driven development. Read the steering docs as project memory before non-trivial work, and run feature work through the spec flow below.
Project context
- Steering (
.kiro/steering/{product,structure,tech}.md) — project-wide rules and context. Load as project memory. - Specs (
.kiro/specs/<feature>/) — one directory per feature:spec.json,requirements.md,design.md,tasks.md, and areview.mdafter review. - Rules + templates (
.kiro/settings/) — the spec engine.rules/holds the authoring/review gates;templates/holds the artifact skeletons.
Spec flow (human-approved gates)
Author each artifact from its template in .kiro/settings/templates/, self-check it against the matching gate in .kiro/settings/rules/, then get user approval before moving on. There are no /kiro-* slash commands in this repo — the flow is driven manually.
- Requirements →
templates/specs/requirements.md, gaterules/requirements-review-gate.md+rules/ears-format.md. EARS acceptance criteria, numeric IDs only. - Design →
templates/specs/design.md, gaterules/design-review-gate.md+rules/design-principles.md. Boundary sections + file plan + full requirements traceability (explicit IDs, no ranges). - Tasks →
templates/specs/tasks.md, gaterules/tasks-generation.md+rules/tasks-parallel-analysis.md. Foundation → Core → Validation;(P)only for non-overlapping boundaries. - Implementation — code to the approved design, then a review pass (e.g. parallel doc + implementation reviewers) before landing. Record outcomes in
review.md.
Update spec.json phase/approvals as each gate passes. Steering edits follow rules/steering-principles.md (patterns, not file trees).
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.
- 7d ago First seen · 42 lines · 748 tokens per session scan A a7b6c2c65d56
mcp-custos CLAUDE.md is an instructions file published in the GitHub repository an0malous/mcp-custos (3 stars, last pushed 1mo ago), licensed MIT. It adds 748 tokens to every session, about $0.0037 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.