Monty is a minimal Python interpreter written in Rust that runs AI-generated code in a restricted environment without direct filesystem, environment-variable, or network access. It is for AI agents that need to execute Python and type-checking tasks while allowing developers to control which host functions and objects the code can use, and the catalogue entries integrate it into agent workflows.
Borrowing it
Nothing to install: this file belongs to pydantic/monty. 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/pydantic/monty/main/.agents/skills/review-verbosity/SKILL.mdgit clone --depth 1 https://github.com/pydantic/montyWrote 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/skills/pydantic/monty/review-verbosity)<a href="https://agentmods.dev/skills/pydantic/monty/review-verbosity"><img src="https://agentmods.dev/badge/skills/pydantic/monty/review-verbosity/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/skills/pydantic/monty/review-verbosity"><img src="https://agentmods.dev/badge/skills/pydantic/monty/review-verbosity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00471 |
| Opus 5.5 | $0.00017 | $0.00188 |
| Sonnet 5.5 | $0.00009 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
review-verbosity 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 1mo 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
Verbosity review
New comments and docstrings are usually too verbose. Rewrite them concisely. This skill edits — it doesn't just report.
git diff --stat origin/main...HEAD # which crates changed
git diff origin/main...HEAD
Dispatch one sub-agent per changed area — a crate, or any other group of changed files,
so nothing outside crates/ is missed — then review their edits yourself. A single pass
over a large diff won't be exhaustive. In every comment the branch touched:
- Cut it down. Comments and field docstrings rarely over 3 lines, mostly 1; function and struct docstrings <= 5.
- Delete tautology — restating what the code plainly says earns nothing.
- Delete narration of the obvious, restated type signatures, how the code came to be, hedging.
- Keep the motivation — why the code exists and its foot-guns are the valuable part. Don't cut real information to hit a line count.
- Drop over-long examples. Public items only, <= 8 lines, and every one must run in
tests — never
ignore. - Fix what's out of date. A comment the branch made wrong gets corrected, not left.
Python docstrings are markdown: single backticks, never RST double-backticks.
Only touch what this branch added or changed, unless asked for a wider sweep. Don't change behaviour — if a comment is wrong because the code is wrong, say so rather than rewording it to match. Concision, not terseness: an unfollowable comment is worse than a long one.
make format-rs && make lint-rs
git diff --stat # format-rs is `cargo +nightly fmt --all` — check it touched only your files
Then report what you cut, by file, in a couple of lines — not a full inventory.
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.
- 1mo ago Changed af95de78d95d
- 2mo ago First seen · 44 lines · 43 tokens per session scan A d07eb7df7a56
review-verbosity is a skill published in the GitHub repository pydantic/monty (8,801 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 471 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
github-code-review
Review code changes by analyzing git diffs, leaving inline comments on PRs, and performing thorough pre-push review. Works with gh CLI or falls back to git + GitHub REST API via curl.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
requesting-code-review
Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.
fast-rust
Practical guidance for writing, refactoring, and reviewing fast, reliable, and maintainable Rust code.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
feature-flag-conventions
Cargo features: shared otel/mcp/allocator contract, then Xberg's ORT-free targets, aggregates, PDF backend, parity guard. Use when editing [features].