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/kardaj/openapi-tools-mcp/agents-mdgit clone --depth 1 https://github.com/kardaj/openapi-tools-mcpWhat 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.00251 | $0.00251 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
openapi-tools-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 2d 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
- never use
pip. Useuv pipinstead. - keep
README.mdup to date whenever the server changes.
Design Philosophy
- MCP tools should be self-describable: generated tool descriptions, parameter schemas, README examples, and tests should tell the same story without requiring users to inspect implementation code.
- Keep the public tool surface small and flexible: prefer extending existing tools and input shapes when that preserves compatibility, and avoid adding narrowly scoped tool names unless a distinct workflow genuinely requires one.
Quality Gates
- MCP server self-documentation is part of the public API. When a change affects tool behavior, inputs, outputs, caching, errors, or supported sources, the implementation quality gate must inspect generated MCP tool metadata and verify that descriptions and parameter schemas are up to date with the shipped features. Add or update regression tests for generated tool metadata when practical.
Agent Workflow
This section is managed by agent-flow sync; do not edit it directly. Add project-specific instructions outside the agent-flow markers.
- Before making implementation changes, checking PR state, addressing PR comments, or running PR checks, read and follow
prompts/agent-flow-implement.md.
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.
- 2d ago First seen · 20 lines · 251 tokens per session scan A 87e41652e1fd
openapi-tools-mcp AGENTS.md is an instructions file published in the GitHub repository kardaj/openapi-tools-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 251 tokens to every session, about $0.0013 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.