Borrowing it
Nothing to install: this file belongs to WCAG-Compliance/wcagc-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WCAG-Compliance/wcagc-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/WCAG-Compliance/wcagc-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/wcag-compliance/wcagc-mcp/agents-md)<a href="https://agentmods.dev/instructions/wcag-compliance/wcagc-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wcag-compliance/wcagc-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/wcag-compliance/wcagc-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wcag-compliance/wcagc-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01208 | $0.01208 |
| Opus 5 | $0.00604 | $0.00604 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
wcagc-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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — wcagc-mcp (Node/TS, MCP server)
A thin, stateless adapter: it translates MCP tool calls into HTTP calls against wcagc-api, forwarding the caller's own bearer. No database, no scan logic, no secrets beyond WCAGC_API_BASE_URL. Authentication, entitlements, quotas and scan orchestration all live in the API — keep it that way.
Unlike the other services, this one leaves the monorepo twice: as public source (WCAG-Compliance/wcagc-mcp) and as a public npm package (@wcagc/mcp). Both are mirrored automatically; never push to either by hand.
1. ⚠️ Bump the version — every change that ships
If you change anything under wcagc-mcp/src/, you MUST raise the version. The version is the release trigger: mcp.yml publishes to npm and to the MCP Registry only when package.json's version differs from the previous commit's. Forget it and your change silently deploys to Fly while every local npx @wcagc/mcp user stays on the old build — the two drift apart with nothing pointing it out.
Use the script — do not hand-edit the version anywhere:
npm run set-version 0.2.6
It moves all four places that must agree (package.json version, server.json version and packages[0].version, and src/server.ts VERSION) and verifies the result. Editing them by hand is how a bump reaches CI half-applied — npm run verify then fails on test/version.test.ts, which is the safety net working, but it costs a red pipeline for nothing.
That net catches the four disagreeing with each other. Nothing catches a version you never bumped at all — that part is on you.
Semver, judged by what an MCP client sees:
- patch — internal fix, no change to tool names, arguments or output shape.
- minor — new tool, new optional argument, new output field.
- major — renamed/removed tool, changed argument semantics, changed output shape.
Docs-only or test-only edits do not need a bump.
2. Releasing is automatic — do not run publish commands
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.
- 9d ago First seen · 66 lines · 1,208 tokens per session scan A 2d6b8b24df34
wcagc-mcp AGENTS.md is an instructions file published in the GitHub repository WCAG-Compliance/wcagc-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 1,208 tokens to every session, about $0.0060 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
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.
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.
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).
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.