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 skills add Jartan-LLC/grimoire --skill review-prgit clone --depth 1 https://github.com/Jartan-LLC/grimoireWrote 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/jartan-llc/grimoire/review-pr)<a href="https://agentmods.dev/skills/jartan-llc/grimoire/review-pr"><img src="https://agentmods.dev/badge/skills/jartan-llc/grimoire/review-pr/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/jartan-llc/grimoire/review-pr"><img src="https://agentmods.dev/badge/skills/jartan-llc/grimoire/review-pr.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.00011 | $0.00353 |
| Opus 5 | $0.00005 | $0.00177 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
review-pr 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 10d 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
Review PR
Review a pull request with category-based reviewer agents.
Process
1. Get PR Context
Determine the PR number from the user's request, which may carry context beyond the number. Fetch the PR details and diff:
gh pr view <pr-number>
gh pr diff <pr-number>
2. Categorize and Review
Launch relevant reviewer agents based on changed files:
- Backend changes ->
backend-reviewer - Frontend changes ->
frontend-reviewer - Documentation changes, or code that changes public behavior ->
doc-reviewer - CI/test changes ->
test-reviewer - Non-trivial code changes ->
structure-reviewer - All changes ->
general-reviewer
3. Verify Documentation
If code changed public behavior, doc-reviewer must run -- it owns doc-code mismatch.
4. Post Review
Reviewers flag findings they could not confirm as suspected (they have no web access, and some issues resist static reading). Before posting, resolve each: verify post-cutoff versions against a live source, confirm others by re-reading the code; post anything still unresolved under Suspected as a question -- never silently dropped. Then post the review as a PR comment following review-format.md in the gitwise:github-conventions skill, ending with the reply hint -- reply with /praxis:address-review <pr-number> to work through findings:
gh pr comment <pr-number> --body "<review comment>"
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.
- 10d ago First seen · 44 lines · 11 tokens per session scan A c24def80af45
review-pr is a skill published in the GitHub repository Jartan-LLC/grimoire (2 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 353 once invoked, about $0.0001 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 skills, from other repositories
babysit-pr
Resolve reviewer comments on a pull request or pasted feedback using a six-step evidence-grounded protocol. Use when asked to resolve review feedback, address reviewer comments, process PR comments, triage review feedback, apply review suggestions, handle code review feedback, decide which review comments to accept or…
pr-history-hygiene
Keep pull-request history deliberate and safe — split independent changes, rewrite with lease-protected force-push (never raw force), apply one kind label plus all material area labels, and land a stack of dependent PRs through the platform's native stack feature rather than manually merging and retargeting. Use when…
cm-code-review
Full review lifecycle — request reviews, handle feedback with technical rigor, and complete branch integration. Use when completing tasks, receiving feedback, or finishing feature branches.
pr-from-diff
Write a PR description a reviewer can approve fast. Use when opening any pull request.
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…