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/joeybe1/mcp-augment/agents-mdgit clone --depth 1 https://github.com/JoeyBe1/mcp-augmentWrote 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/joeybe1/mcp-augment/agents-md)<a href="https://agentmods.dev/instructions/joeybe1/mcp-augment/agents-md"><img src="https://agentmods.dev/badge/instructions/joeybe1/mcp-augment/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 | $0.00321 | $0.00321 |
| Opus 5 | $0.00161 | $0.00161 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
mcp-augment 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 3d 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.
What it actually says
AGENTS.md — Guidelines for agents in this repository
This file is the public agent brief for the mcp-augment project. It omits private workflow rules that belong only in a full dev checkout.
Project
- Purpose: Provide an MCP server and hook layer so AI coding tools can enforce safer file and shell operations (
safe_*tools + Pre/Post hook chain). - Language: Python 3.10+
- Key paths:
project-tools/mcp-hooks-server/,.kilo/hooks/,tests/.
Build / test
export PROJECT_DIR="$(pwd)" # repository root; required for many tests and runtime
pip install -U pip mcp
pip install pytest hatchling # hatchling if you use pip install -e . once wheel layout exists
pip install -e . # optional; prod tree may use pip install mcp + pytest only
pytest tests/ -q --tb=short
For HTTP integration tests, start the stack (see root README.md), then run python3 tests/mcp_protocol_test.py and related smoke tests.
Code style
- Prefer clear, small functions; type hints on public APIs.
- Follow existing patterns in
project-tools/mcp-hooks-server/. - Do not commit secrets, API keys, or machine-specific absolute paths in shipped files.
Scope
- Keep changes focused on the user-facing MCP + hooks story.
- Propose larger refactors in an issue or PR description before broad rewrites.
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.
- 3d ago First seen · 33 lines · 321 tokens per session scan A 754fdd9b742d
mcp-augment AGENTS.md is an instructions file published in the GitHub repository JoeyBe1/mcp-augment (0 stars, last pushed 5mo ago), licensed MIT. It adds 321 tokens to every session, about $0.0016 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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.