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 skills/thermiteau/maverick/do-pullrequest-reviewnpx skills add thermiteau/maverick --skill do-pullrequest-reviewgit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/thermiteau/maverick/do-pullrequest-review)<a href="https://agentmods.dev/skills/thermiteau/maverick/do-pullrequest-review"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/do-pullrequest-review.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 | $0.00043 | $0.01462 |
| Opus 5 | $0.00022 | $0.00731 |
| Sonnet 5 | $0.00009 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
do-pullrequest-review 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Receiving Code Review
Code review feedback requires technical evaluation, not automatic agreement. Verify before implementing. Push back when the feedback is wrong.
Preflight (mandatory)
Run this first. If it exits non-zero, halt and report the stderr output to the user verbatim. Do not proceed.
uv run maverick preflight do-pullrequest-review
Skip the preflight when invoked from inside a do-issue-* or
do-epic phase — the orchestrator already ran a stricter one this
session. Run it only when this skill is invoked standalone.
The check verifies the project is initialised and gh/uv are on PATH.
The Response Pattern
digraph receive_review {
"Receive feedback" [shape=box];
"Read all items completely" [shape=box];
"All items understood?" [shape=diamond];
"Ask for clarification on unclear items" [shape=box];
"Verify each item against codebase" [shape=box];
"Item technically correct?" [shape=diamond];
"Implement fix" [shape=box];
"Push back with reasoning" [shape=box];
"Run verification after each fix" [shape=box];
"More items?" [shape=diamond];
"Run full verification suite" [shape=box];
"Receive feedback" -> "Read all items completely";
"Read all items completely" -> "All items understood?";
"All items understood?" -> "Verify each item against codebase" [label="yes"];
"All items understood?" -> "Ask for clarification on unclear items" [label="no"];
"Ask for clarification on unclear items" -> "Verify each item against codebase";
"Verify each item against codebase" -> "Item technically correct?";
"Item technically correct?" -> "Implement fix" [label="yes"];
"Item technically correct?" -> "Push back with reasoning" [label="no"];
"Implement fix" -> "Run verification after each fix";
"Run verification after each fix" -> "More items?";
"Push back with reasoning" -> "More items?";
"More items?" -> "Verify each item against codebase" [label="yes"];
"More items?" -> "Run full verification suite" [label="no"];
}
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 · 163 lines · 43 tokens per session scan A 531716d9779b
do-pullrequest-review is a skill published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,462 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…