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/wagtail/wagtail-mcp/agents-mdgit clone --depth 1 https://github.com/wagtail/wagtail-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/wagtail/wagtail-mcp/agents-md)<a href="https://agentmods.dev/instructions/wagtail/wagtail-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wagtail/wagtail-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.00504 | $0.00504 |
| Opus 5 | $0.00252 | $0.00252 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
wagtail-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.
What it actually says
Agents
Important context for AI coding agents working on this project.
Project overview
Wagtail MCP is a Django/Wagtail package. The source code is in src/wagtail_mcp/, with tests in tests/ and a demo Wagtail site in demo/.
This project was created from the cookiecutter-wagtail-package template and follows the Wagtail package maintenance guidelines.
Key commands
just help # View all commands
just install # Install Python and Node.js dependencies
just demo # Run the demo Wagtail site (migrate + load data + runserver)
just test # Run tests with pytest
just lint # Run all linters (Ruff, prek, Prettier, Stylelint)
just format # Run all formatters (Ruff, Prettier)
just coverage # Run tests with coverage report
Quality assurance
- Python: Ruff for linting and formatting (
ruff.toml), prek hooks (prek.toml). - JavaScript/CSS/JSON/YAML: Prettier for formatting (
prettier.config.js). - CSS: Stylelint with
@wagtail/stylelint-config-wagtail(stylelint.config.mjs). - Tests: pytest with pytest-django. Test settings are in
src/wagtail_mcp/test/settings.py. - CI: GitHub Actions in
.github/workflows/.
Always run just lint and just test before considering work complete.
Project layout
src/wagtail_mcp/ # Package source code
src/wagtail_mcp/test/ # Django test app with settings, URLs
tests/ # Test modules (pytest)
demo/ # Demo Wagtail site for development
.github/workflows/ # CI: linting, tests, nightly builds, publishing
Guidelines
- Follow Semantic Versioning for releases.
- Use Keep a Changelog format for CHANGELOG.md.
- CSS should follow the Wagtail stylelint config conventions.
- Refer to CONTRIBUTING.md for the full contribution workflow.
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 · 49 lines · 504 tokens per session scan A 2ab4b20b985b
wagtail-mcp AGENTS.md is an instructions file published in the GitHub repository wagtail/wagtail-mcp (3 stars, last pushed 9d ago), licensed BSD-3-Clause. It adds 504 tokens to every session, about $0.0025 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
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).