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 chrono-meta/forge-harness --skill harness-pr-reviewergit clone --depth 1 https://github.com/chrono-meta/forge-harnessWrote 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/chrono-meta/forge-harness/harness-pr-reviewer)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/harness-pr-reviewer"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/harness-pr-reviewer/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/chrono-meta/forge-harness/harness-pr-reviewer"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/harness-pr-reviewer.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.00061 | $0.05501 |
| Opus 5.5 | $0.00024 | $0.02200 |
| Sonnet 5.5 | $0.00012 | $0.01100 |
| Haiku 4.5 | $0.00006 | $0.00550 |
Grade A, and why
harness-pr-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: The original developer is the forge-harness original developer (development source + meta-monitoring home). In external user install environments, the install environment user themselves is the baseline integrity gate operator (following path B generalization baseline /
SKILL_detail.md §External User Environment Adaptation Path§).
harness-pr-reviewer — Hub Gate Operation Rule Automation
When a PR is submitted, checks consistency against the user environment's baseline assets (CLAUDE.md · memory · naming · asset classification) and attaches a review comment. 5-step: diff read → 8-matrix check → self-catch → comment attachment → merge recommendation.
Activation Triggers
Renamed from
hub-cc-pr-reviewer(2026-09-12, operator decision). The old name said where it was born (the hub's own cc reviewing its own PRs). What it actually is — measured on qasp/pmh PRs in 2026-09 — is the standalone doorway through which a field harness verifies its own submitted PR with FH's review capability. Old-name utterances ("hub-cc-pr-reviewer", "hub review", "hub cc review") still route here; downstream forks that carry the old directory name (PMH) keep working until they sync. No redirect stub directory is shipped (same policy asphantom-quench).
- PR #N input: "Review PR #N" / "Check PR #N" / "hub review" (old-name alias) / "harness PR review" / "baseline consistency check"
- Action leader cc → hub sync point: Large decision area PR catch (following Option C Hybrid policy — memory creation / CLAUDE.md change / CATALOG round / skill v0.x evolution / policy change / asset synergy branch judgment)
- Hub cc session entry: Layer A auto-read recent external commit catch (auto-discover new PRs)
Natural Language Triggers (General user phrasing — activates without internal vocabulary)
| Example phrasing | Intent |
|---|---|
| "Is it okay to submit this PR?" | PR review request |
| "This change seems inconsistent with existing rules" | Baseline consistency check |
| "Please review before merging" | PR review gate |
| "Does this change affect other parts?" | Consistency check |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 327 lines · 61 tokens per session scan A d7be9a5d7ea3
harness-pr-reviewer is a skill published in the GitHub repository chrono-meta/forge-harness (30 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 5,501 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-09-12.
Other skills, from other repositories
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
batch-member-cites-a-path-only-a-non-member-adds
You wrote something correct that the default reader cannot reach: a batch member citing a path only a NON-member adds, or a rule, ruling or ledger sitting on an unlanded branch.
working-tree-edits-stranded-on-squash-merge
Diagnose and prevent "I made the fix but it's not on main" cases where the fix was applied in the working tree via Edit / Write but never git added before the squash-merge. Use when: (1) you squash-merged a PR and the user reports the issue is back, (2) git status after the merge shows uncommitted changes for files…
b3os-github-workflow
A GitHub workflow for taking code changes from an isolated branch through a pull request, review, approval, merge, and post-merge check. A pull request is a proposal to merge changes into a shared repository.
pr-authoring
Playbook for deployment-aware pull requests — the 11-section format that turns a PR into a reviewable contract; why, decision requested, change map, review order, evidence, verification, risk, rollback. Used for the Define→build handoff and any PR a great-pm-driven project opens.