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/qipeijun/swagger-docs-mcp/agents-mdgit clone --depth 1 https://github.com/qipeijun/swagger-docs-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/qipeijun/swagger-docs-mcp/agents-md)<a href="https://agentmods.dev/instructions/qipeijun/swagger-docs-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/qipeijun/swagger-docs-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 | $0.00597 | $0.00597 |
| Opus 5 | $0.00298 | $0.00298 |
| Sonnet 5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
swagger-docs-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 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.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Source code lives in src/ and is organized by responsibility. source/ handles safe HTTP fetching and document discovery; navigation/ parses Knife4j links; parser/ defines parser contracts; swagger2/ implements Swagger 2.0 parsing; service/ contains client-independent query logic; server/ exposes MCP tools; and cli/ implements setup and diagnostic commands. Shared domain models are in src/domain/. Tests mirror these concerns under tests/, with reusable data in tests/fixtures/ and HTTP helpers in tests/helpers/. Compiled output belongs in dist/ and must not be edited or committed.
Build, Test, and Development Commands
npm ci: install the exact dependencies recorded inpackage-lock.json.npm run dev: run the TypeScript entry point directly withtsx.npm run typecheck: check strict TypeScript constraints without emitting files.npm test: run the complete Vitest suite once.npm run test:integration: run only the MCP integration test.npm run build: compile production ESM and declarations intodist/.npm run check: run type checking, all tests, and the production build; use this before a pull request. A full build is not required for every small documentation-only change.
Node.js 20 or newer is required. After building, run node dist/index.js doctor <docs-url> for a live smoke test.
Coding Style & Naming Conventions
Use strict TypeScript, two-space indentation, double quotes, semicolons, and .js extensions in relative ESM imports. Use camelCase for functions and variables, PascalCase for types and enums, and uppercase enum members. Add concise comments for status enums, non-obvious business rules, and public helper contracts. Do not add speculative compatibility fallbacks; ask when an external contract is unclear. No formatter or linter is currently configured, so follow nearby code and rely on npm run typecheck.
Testing Guidelines
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 · 30 lines · 597 tokens per session scan A dd916d287f69
swagger-docs-mcp AGENTS.md is an instructions file published in the GitHub repository qipeijun/swagger-docs-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 597 tokens to every session, about $0.0030 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
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Copilot instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.
cyxj-groksearch CLAUDE.md
Claude Code instructions for chenyuxiaojin/cyxj-groksearch, covering claude.md, 常用命令 and 结构与坑.
minecraft-dev-mcp AGENTS.md
Instructions for MCDxAI/minecraft-dev-mcp, covering agent handbook – minecraft dev mcp, project snapshot, what agents should prioritize, architecture wayfinder (src/) and available mcp tools (for llm surfaces).
bray AGENTS.md
AGENTS.md instructions for forgesworn/bray, covering agents.md — nostr-bray, what this is, build & test, architecture and tool groups.