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/chapmanjw/rutherford-mcp-server/agents-mdgit clone --depth 1 https://github.com/chapmanjw/rutherford-mcp-serverWrote 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/chapmanjw/rutherford-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/chapmanjw/rutherford-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/chapmanjw/rutherford-mcp-server/agents-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.01827 | $0.01827 |
| Opus 5 | $0.00914 | $0.00914 |
| Sonnet 5 | $0.00365 | $0.00365 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
rutherford-mcp-server 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 6d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for coding agents working in this repository, and the canonical home for it. Written to the AGENTS.md convention so any agent finds the same contract rather than each one needing a file named after its vendor.
CLAUDE.md still exists, because Claude Code reads that name and not this one; it imports this file
and holds nothing of its own. Anything that belongs to every agent belongs here.
Humans want CONTRIBUTING.md, which covers the same ground at more length and adds the review and pull-request expectations.
Commands
uv sync # install deps (project + dev group) into .venv
uv run ruff check . # lint
uv run ruff format . # format (write)
uv run ruff format --check . # format check (CI mode)
uv run mypy # type-check (strict)
uv run python scripts/check_license_headers.py # license-header check
uv run pytest # unit tests only (integration deselected by default)
uv run pytest -m integration # local-only suite that drives real ACP agents
A justfile wraps these. just check is the pre-push gate: it runs scripts/gate.py, which executes
every stage in order (lint, format-check, license-check, typecheck, tests, the per-file coverage floor,
the entrypoint smoke check, and the build), streams their output, and stops at the first failure.
just test-integration drives the real agents. Run a single test file with
uv run pytest tests/test_session.py.
If you are an agent, read the verdict rather than the prose. The gate writes
.tmp/gate-report.toon, which names the stage that failed instead of leaving you to parse output meant
for a human:
schema: 1
head: <sha>
dirty: false # true means uncommitted edits were in the tree, so `head` alone does not describe what ran
verdict: pass # or fail
failed_stage: null # the stage name when verdict is fail
stages[8,]{name,ok,seconds,exit_code}:
lint,true,0.08,0
...
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.
- 6d ago First seen · 141 lines · 1,827 tokens per session scan A a43bd52b010d
rutherford-mcp-server AGENTS.md is an instructions file published in the GitHub repository chapmanjw/rutherford-mcp-server (6 stars, last pushed yesterday), licensed MIT. It adds 1,827 tokens to every session, about $0.0091 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
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).
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 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.
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.