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.
git clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/commands/notque/vexjoy-agent/pr-review)<a href="https://agentmods.dev/commands/notque/vexjoy-agent/pr-review"><img src="https://agentmods.dev/badge/commands/notque/vexjoy-agent/pr-review/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/commands/notque/vexjoy-agent/pr-review"><img src="https://agentmods.dev/badge/commands/notque/vexjoy-agent/pr-review.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.00014 | $0.03170 |
| Opus 5.5 | $0.00006 | $0.01268 |
| Sonnet 5.5 | $0.00003 | $0.00634 |
| Haiku 4.5 | $0.00001 | $0.00317 |
Grade A, and why
pr-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 today.
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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive PR Review (with Retro Learning)
Comprehensive PR review using specialized agents, with automatic knowledge capture.
This is a local fork of pr-review-toolkit:review-pr with a retro learning phase that
records review patterns to learning.db.
Scope
This command accepts either a PR reference or a local branch diff. You do not need an open PR to use it.
| Invocation form | What it reviews |
|---|---|
/pr-review (no argument) |
Uncommitted and committed local changes against the base branch (HEAD vs base) |
/pr-review 123 or /pr-review https://github.com/org/repo/pull/123 |
The diff of the specified open PR |
Review the local commit before any push. In a repo that is not a non-fork github.com/notque repo (sapcc, SAP-cloud-infrastructure, cloudoperators, perses, ceph, every github.wdf.sap.corp org, other upstreams, and notque forks), nothing reaches a remote before this review passes: no push, remote branch, or draft PR. Commit first, review the local commit, fix, review the fix delta, then push. The pretool-review-before-push-gate hook enforces this with the record from Phase 6b.
When no argument is provided, the command reads git diff to determine changed files. When a PR number or URL is provided, it fetches the PR diff via gh pr view. All review phases and retro learning apply in both cases.
Usage
/pr-review # Full review (all aspects)
/pr-review tests errors # Specific aspects only
/pr-review all parallel # All agents in parallel
Related: /pr-review-address-feedback — Process existing GitHub reviewer comments (validate-then-fix workflow)
Review Aspects
- comments - Analyze code comment accuracy and maintainability
- tests - Review test coverage quality and completeness
- errors - Check error handling for silent failures
- types - Analyze type design and invariants (if new types added)
- code - General code review for project guidelines
- simplify - Simplify code for clarity and maintainability
- all - Run all applicable reviews (default)
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.
- today Changed · +19 lines b840bfe3e404
- yesterday Changed · +1 tokens per session fb201d4c7191
- 1mo ago Changed 639c4b4b3c9f
- 1mo ago First seen · 273 lines · 13 tokens per session scan A 85119791a870
pr-review is a command published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 3,170 once invoked, about $0.0001 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 commands, from other repositories
pr-description
Write a pull request description that helps reviewers: what changed, why, and how to verify, from a diff.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.