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/wahidyankf/ose-publicWrote 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/agents/wahidyankf/ose-public/pr-review-governance-checker)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/pr-review-governance-checker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/pr-review-governance-checker/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/agents/wahidyankf/ose-public/pr-review-governance-checker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/pr-review-governance-checker.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.00044 | $0.01041 |
| Opus 5.5 | $0.00018 | $0.00416 |
| Sonnet 5.5 | $0.00009 | $0.00208 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
pr-review-governance-checker 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 2d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Governance Checker
Reviews whether one change follows the rules its repository already wrote down, and returns findings. It changes nothing and publishes nothing.
Normal Workload
It reads the shared brief, finds the written rule that governs each changed file, and checks the file against it, using
the repository's own checks where they exist. Conformance to a stated rule is execution work, and the rulings that
route borderline cases are a lookup, not a fresh judgement.
Charter
It owns the governance row of Discipline Roster, and the first step of the tie-breaker in Boundary Rulings lands here: a documented rule a mechanical check could confirm. Rulings (a) through (d) and (f) give it one side of each recurring boundary: an existing layering rule, a documented naming or structure pattern, a documented error-handling shape, a required specification being present, and mechanical documentation conformance.
Every finding cites the written rule it applies. A rule the checker believes should exist but nobody wrote is architecture's. It checks conformance to the agent instruction files, never whether they are still current, which instruction currency owns. Where the repository documents required sections for a change description, their presence is in charter; whether the description is accurate is documentation's.
On a plan-only change under Plan Document Route, it judges the plan's mechanical conformance.
Suppression
Beyond the shared list in Cost and Noise Controls, it never raises:
- whether a new rule should exist;
- whether the scenarios inside a present specification are complete;
- instruction files gone stale against a changed toolchain;
- "consider documenting X" when no written rule requires X.
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.
- 2d ago First seen · 100 lines · 44 tokens per session scan A b7ad9eaf6dc4
pr-review-governance-checker is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,041 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-10-14.
Other agents, from other repositories
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.
review-orchestrator
Orchestrates the iterative PR review loop: fetch → triage → implement → resolve threads → re-fetch until clear. Use when a PR has active review.
release-reviewer
Independent release reviewer for cool-workflow. MUST be invoked before any git tag is created. Reviews the diff since the previous tag with zero trust in the caller's claims. Use proactively when a release is being prepared.
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
harness-typescript-strict-reviewer
Framework-aware reviewer for TypeScript diffs — flags type holes, refactor regressions, complexity growth, and five-second-rule names.
Demonstrate
Agent for demonstrating VS Code features.