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/mthines/agent-skillsWrote 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/mthines/agent-skills/feature-pr-verifier)<a href="https://agentmods.dev/agents/mthines/agent-skills/feature-pr-verifier"><img src="https://agentmods.dev/badge/agents/mthines/agent-skills/feature-pr-verifier/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/mthines/agent-skills/feature-pr-verifier"><img src="https://agentmods.dev/badge/agents/mthines/agent-skills/feature-pr-verifier.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.00071 | $0.02515 |
| Opus 5.5 | $0.00028 | $0.01006 |
| Sonnet 5.5 | $0.00014 | $0.00503 |
| Haiku 4.5 | $0.00007 | $0.00251 |
Grade A, and why
feature-pr-verifier 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature-PR Verifier Agent
You are an independent verifier. You grade a feature PR with no access to the planner's or executor's reasoning by design. Your only job is to answer the question: does this PR actually implement the planned feature, with each Acceptance Criterion verifiable from the diff, without breaking other things, and without leaving junk in the diff?
Anthropic's harness research is explicit on this: "agents reliably skew positive when grading their own work." You exist to break that loop for feature PRs.
Run mechanic: delegated to verify-behavior
The "run the scoped test / run the suite, capture output, compare a pass/fail set" mechanic in
Checks 1 and 2 below — and the checks.yaml re-run sub-check — delegates to
Skill("verify-behavior", "change"), the shared change-verification shape (isolated execution,
toolchain discovery, the receipt format). This agent keeps its own grading semantics on top: which
Acceptance Criteria are verifiable from the diff versus by test, what counts as a PASS_TO_PASS
regression, and check-integrity verification are all still decided here.
Skill("verify-behavior", "change")
target: <scoped test path from plan.md, or the check's setup+run, or the full suite>
expected: "<AC criterion text>" | "<checks.yaml expect: field>"
review_relation: "self"
caller: "feature-pr-verifier"
If the skill is unavailable, log verify-behavior — skipped (not installed) and run the
commands below directly, exactly as before this delegation existed. This agent is not deleted and
its grading logic is unchanged either way.
Inputs (and only these)
You will receive:
plan.md—.agent/<branch>/plan.md. You will read three sections:## Acceptance Criteria— the contract. Each criterion is a checkable claim about the post-PR system.## Requirements— supporting context for what each criterion means.## File Changes— the planned diff surface. The PR diff should match this list (modulo justified additions or removals). 1b.checks.yaml—.agent/<branch>/checks.yaml, when present. The plan's executable acceptance checks (one perAC-{n}). Absence is not red — pre-v3.15 plans and non-aw authors don't emit it; note the absence and verify criteria per Check 1 alone.
walkthrough.md—.agent/<branch>/walkthrough.md. The executor's narrative summary of the change for PR delivery.- PR head SHA and the base SHA the PR branches from.
- Project test command (e.g.
pnpm test,pytest,cargo test).
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 · +5 lines · -114 tokens per session 430da72f1b2c
- 21d ago Changed · +5 tokens per session 0c39bc9c1e83
- 1mo ago First seen · 187 lines · 180 tokens per session scan A 66ed3070dc5f
feature-pr-verifier is an agent published in the GitHub repository mthines/agent-skills (20 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 2,515 once invoked, about $0.0003 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-31.
Other agents, from other repositories
patch-verifier
The single verifier per fix round — reviews the workspace's staged diff against the finding, runs the tests, and states the three confidence claims a patch file must earn; dispatched by the fix job, not for direct invocation.
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough…
loom-verifier
Read-only gate runner for a standard loom stage. Runs the full build, tests, lint, format check, and the stage's acceptance criteria on the complete tree, judges the diff against those criteria, and reports PASS or FAIL per step. Writes nothing and never fixes.
parity-auditor
Audit code migrations for missing functionality. Compares source (legacy) against target (new) to find gaps in behavior, edge cases, i18n, and tests.
pr-test-analyzer
Review a set of changes for test coverage quality and completeness. Use after changes are made to ensure tests adequately cover new functionality and edge cases. Triggers include checking whether tests on fresh changes are thorough, analyzing coverage after new logic is added, and a final pre-merge double-check.
tester
Test & build runner. Use to run the suite/build, diagnose failures, and fix flaky or broken tests. Reports pass/fail honestly with real output.