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/mmadfox/swag2mcp/agents-mdgit clone --depth 1 https://github.com/mmadfox/swag2mcpWrote 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/mmadfox/swag2mcp/agents-md)<a href="https://agentmods.dev/instructions/mmadfox/swag2mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/mmadfox/swag2mcp/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.01431 | $0.01431 |
| Opus 5 | $0.00715 | $0.00715 |
| Sonnet 5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
swag2mcp 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swag2mcp — Agent Guide
Commands
make lint # golangci-lint (120 line limit, strict linters)
make cover # go test ./... + coverage HTML report (excludes commands, tui, mockserver)
make integration-tests # go test -v -count=1 -timeout 600s ./tests/...
make testall # lint + integration-tests + go test ./...
go test ./pkg/... # single package
go test ./... # all packages
go generate ./... # installs mockgen + generates mocks (internal/server/mcp)
Order: make lint && go test ./...
Note: make cover-core is declared in the Makefile but has no recipe — do not use it.
Architecture
- Entrypoint:
cmd/swag2mcp/main.go— cobra CLI with 13 subcommands (init, add, delete, ls, run, validate, clean, update, mcp, version, info, import, export) - Mock binary:
cmd/swag2mcp-mock/main.go— separate binary withmockserversubcommand (--tls,--tls-cert,--tls-key) - Core:
internal/service/— business logic (Bootstrap, Invoke, Search, Inspect, Auth, Specs, etc.) - MCP server:
internal/server/mcp/— 16 MCP tools, usesgo.uber.org/mockfor tests; HTTP transport providesGET /healthendpoint - TUI:
internal/tui/— Bubbletea explorer + wizards (seeinternal/tui/AGENTS.md— 382 lines) - Config: YAML, cascade: global → spec → collection (
internal/config/) - Auth: 9 methods in
internal/auth/(none, basic, bearer, digest, hmac, oauth2-cc, oauth2-pwd, api-key, script) - Search: bluge full-text engine (
internal/index/) - IDs: MD5-based (
internal/id/)
CLI reference
Full CLI documentation is in .agents/skills/swag2mcp-cli/SKILL.md (763 lines). Key points:
--versionflag is supported (same asversionsubcommand)mcpprints"MCP server listening on http://<addr><path>"on stdout on startupvalidatechecks thatlocationis a valid OpenAPI/Swagger/Postman file (not just any URL)infoshowsmax_response_sizein human-readable format (e.g."1 KB")export/importsupports full workspace round-trip:exportcreates a ZIP backup,import --from-ziprestores it;import --specdownloads all collection spec files from the config and updates locations to local paths
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 · 83 lines · 1,431 tokens per session scan A 83da12cb9cba
swag2mcp AGENTS.md is an instructions file published in the GitHub repository mmadfox/swag2mcp (0 stars, last pushed 24d ago), licensed Apache-2.0. It adds 1,431 tokens to every session, about $0.0072 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
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.