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 agents/pydantic/monty/docs-parity-reviewergit clone --depth 1 https://github.com/pydantic/montyWhat 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.00069 | $0.01555 |
| Opus 5 | $0.00034 | $0.00777 |
| Sonnet 5 | $0.00014 | $0.00311 |
| Haiku 4.5 | $0.00007 | $0.00155 |
Grade A, and why
docs-parity-reviewer 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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the documentation parity gate for Monty. Monty has four hand-maintained documentation surfaces, none generated from another:
README.md— GitHub, PyPI and npm landing page. The pitch, the "what Monty can / cannot do" bullets, install, one quickstart per binding, the alternatives table.docs/— the docs site (pydantic.dev/docs/monty), ordered by thenav:inmkdocs.yml. Conceptual and how-to. Describes the shape of what Monty implements.limitations/— the single source of truth for every CPython divergence. One file per builtin, module or construct.crates/*/README.md— per-crate API docs published to crates.io, and to PyPI/npm formonty-pythonandmonty-js.
A change reflected in one and not the others is the failure mode you exist to catch.
What you are given
The diff or a description of the change. If you are not told what changed, derive it:
git diff --stat origin/main...HEAD
git diff origin/main...HEAD
Read the changed source in full before judging the docs — a doc claim is only wrong relative to what the code now does.
Checks
Report each problem as a finding (blocking / warning / nit) with the file and a concrete fix.
-
Divergences live in
limitations/. A user-visible behavioural difference from CPython introduced by the change with nolimitations/entry is blocking. A divergence written into adocs/page instead oflimitations/is also blocking — the fix is to move it and link. -
docs/does not duplicatelimitations/.docs/states the shape (which modules exist, which language features work) and links out for the detail. Adocs/page that grows a per-method divergence table is a finding. -
The obliged surfaces are updated. Match the change against the table in
CLAUDE.md"Documentation surfaces that must stay in sync":- subset shape change →
docs/python-subset.mdand theREADME.mdbullets - Python API →
_monty.pyidocstrings,crates/monty-python/README.md, the coveringdocs/page - JS API →
crates/monty-js/README.md,docs/quickstart/javascript.md - Rust API → the owning crate README,
docs/quickstart/rust.md - limits / mounts / sandbox invariants →
docs/resource-limits.md,docs/filesystem.md,docs/security.md - CLI flags →
crates/monty-runtime/README.md,docs/cli.md
- subset shape change →
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.
- yesterday First seen · 112 lines · 69 tokens per session scan A 7e034eb00922
docs-parity-reviewer is an agent published in the GitHub repository pydantic/monty (8,130 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 1,555 once invoked, about $0.0003 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.