Borrowing it
Nothing to install: this file belongs to paladini/harness-score. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/paladini/harness-score/main/.agents/skills/pr-release-audit/SKILL.mdgit clone --depth 1 https://github.com/paladini/harness-scoreWrote 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/paladini/harness-score/pr-release-audit)<a href="https://agentmods.dev/skills/paladini/harness-score/pr-release-audit"><img src="https://agentmods.dev/badge/skills/paladini/harness-score/pr-release-audit/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/paladini/harness-score/pr-release-audit"><img src="https://agentmods.dev/badge/skills/paladini/harness-score/pr-release-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.01619 |
| Opus 5.5 | $0.00028 | $0.00648 |
| Sonnet 5.5 | $0.00014 | $0.00324 |
| Haiku 4.5 | $0.00007 | $0.00162 |
Grade A, and why
pr-release-audit 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 29d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR and Release Audit
Perform an evidence-backed audit of the complete change lifecycle. Treat the repository instructions, current branch state, PR metadata, vendor contracts, CI, generated site, and release artifacts as separate evidence surfaces.
Authority and safety
- Read
AGENTS.md, contributor guidance, release guidance, and relevant local rules before changing files. - Preserve unrelated worktree changes. Inspect status before and after edits.
- Review and diagnostics are read-only by default. Implement requested fixes, documentation, or release artifacts when they are in scope.
- Never merge, tag, publish packages, create a GitHub release, close issues, or send external messages unless the user explicitly authorizes that action.
- Do not claim that a change is released, deployed, public, or complete until the corresponding public state has been independently verified.
1. Establish the change boundary
- Identify the repository, PR number, base and head commits, author, linked issue, labels, changed files, and current review/check status.
- Compare the PR with its actual base, not with a stale local branch.
- Classify every changed file as implementation, test, configuration, docs, generated output, release metadata, or unrelated noise.
- Record the initial worktree state and do not overwrite unrelated changes.
2. Review implementation and structure
Check behavior before style:
- correctness, error handling, edge cases, and backward compatibility;
- public API and data-shape contracts, including sync/async behavior;
- path traversal, symlinks, generated files, platform differences, and incomplete or unreadable inputs when relevant;
- security, performance, determinism, and dependency/supply-chain impact;
- whether the design adds the smallest material change or creates a new structural coupling;
- tests for the changed behavior, regression cases, and negative cases.
Reproduce important claims with the project commands. Do not treat a green lint job as proof that behavior, documentation, or release metadata is right.
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.
- 29d ago Changed · +2 lines 81c6950b947e
- 1mo ago Changed · +8 lines 2833036d8ef2
- 1mo ago First seen · 149 lines · 70 tokens per session scan A 74c5ba92188d
pr-release-audit is a skill published in the GitHub repository paladini/harness-score (613 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 1,619 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-09-06.
Other skills, from other repositories
revidere
A Git branch review workflow that groups changes into sections, labels their importance and whether they need attention, and checks that every changed line is explained. It creates a review page with selected differences and links to GitHub.
review-agent-work
Review the changes a CodeAgent session made, and open or review a pull request when the user asks.
review
Self-review code before pushing. Use when the user wants to check their changes, asks 'anything I missed', says 'ready to push', or wants a pre-PR sanity check.
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.