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/respawn-llc/tool-filter-mcp/agents-mdgit clone --depth 1 https://github.com/respawn-llc/tool-filter-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/respawn-llc/tool-filter-mcp/agents-md)<a href="https://agentmods.dev/instructions/respawn-llc/tool-filter-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/respawn-llc/tool-filter-mcp/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.00515 | $0.00515 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
tool-filter-mcp 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 5d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/contains the TypeScript source (CLI entry insrc/index.ts, core proxy logic insrc/proxy.ts, client/transport logic insrc/client.ts, and helpers insrc/utils/).tests/holds unit and integration tests (e.g.,tests/unit/*.test.ts,tests/integration/*.test.ts).dist/is the compiled output produced by the build.docs/andspecs/are supporting materials when present; they are not runtime dependencies.
Build, Test, and Development Commands
npm run build— compile TypeScript todist/using the project tsconfig.npm test -- --run— run the full Vitest suite once (non-watch).npm run lint— run ESLint oversrc/andtests/.npm run format— format TS files via Prettier.npm run format:check— CI-friendly formatting check.
Coding Style & Naming Conventions
- TypeScript 5.x in strict mode; keep typings explicit where inference is unclear.
- 2-space indentation, semicolons, and ESM imports with
.jsextensions (compiled target). - Filenames are kebab-case (e.g.,
tool-list-formatter.ts); types/interfaces use PascalCase. - Formatting and linting are enforced via Prettier and ESLint; keep changes compliant.
Testing Guidelines
- Test framework: Vitest.
- Tests live in
tests/unit/andtests/integration/and use the*.test.tsnaming pattern. - Prefer targeted runs while iterating:
npm test -- --run tests/unit/<name>.test.ts. - Ensure all tests pass before opening a PR.
Commit & Pull Request Guidelines
- Commit messages are short, imperative, and scoped to the change (e.g., “Bump version to 0.4.2”, “Update deps and refresh 2026 maintenance”).
- PRs should include: a brief summary, test command(s) run, and any noteworthy behavior changes.
- Link relevant issues if applicable; no screenshots required for this CLI-only project.
Configuration & Runtime Notes
- Node.js 20+ is required.
- The CLI supports HTTP/SSE and stdio upstream MCP servers; see
README.mdfor usage examples and header/env options.
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.
- 5d ago First seen · 36 lines · 515 tokens per session scan A 1de39fc53479
tool-filter-mcp AGENTS.md is an instructions file published in the GitHub repository respawn-llc/tool-filter-mcp (36 stars, last pushed 3mo ago), licensed MIT. It adds 515 tokens to every session, about $0.0026 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-30.
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).
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.
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).