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/bounded-systems/bounded-tools-mcp/claude-mdgit clone --depth 1 https://github.com/bounded-systems/bounded-tools-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/bounded-systems/bounded-tools-mcp/claude-md)<a href="https://agentmods.dev/instructions/bounded-systems/bounded-tools-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bounded-systems/bounded-tools-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 | $0.00348 | $0.00348 |
| Opus 5 | $0.00174 | $0.00174 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
bounded-tools-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 4d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- verbspec-mcp CLAUDE.md — 100% identical, 0 lines differ
- site-mcp CLAUDE.md — 100% identical, 0 lines differ
What it actually says
{"message":"Not Found","documentation_url":"https://docs.github.com/rest/repos/contents#get-repository-content","status":"404"}
bounded-systems sessions — before anything else
- Bootstrap: run
bash .claude/org-repair.sh— pre-approved where this repo's settings carry the org floor; generator-owned repos may still prompt. Its only trust anchor is the dialog-recorded$ORG_BOOT_SHA256(typed by a human in the environment dialog, never fetched): it executes a local or fetched copy ONLY if the bytes hash to that value, and refuses otherwise.bootstrap in effect→ continue.REFUSEDor a permission denial → stop and report; do not work around it. - Claim before working: dispatch
claim-ticket.ymlinbounded-systems/.github(workflow_dispatch:repo,issue,claimant), then confirm the claim comment ON THE ISSUE names your claimant. Any assignee orclaimedlabel → someone else's. Window unreachable → claim by hand (assign + comment) and say the window was down. No issue → open one. - Degraded mode: no "bounded-systems — Claude context" block in your
session context means the org context did not load. You may claim and work
THIS repo only — no org-level
[settings]/[org]changes, no cross-repo work.
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.
- 4d ago First seen · 22 lines · 348 tokens per session scan A f8b033304e9b
bounded-tools-mcp CLAUDE.md is an instructions file published in the GitHub repository bounded-systems/bounded-tools-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 348 tokens to every session, about $0.0017 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.