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 openshift-eng/ai-helpers --skill pre-commit-reviewgit clone --depth 1 https://github.com/openshift-eng/ai-helpersWrote 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/openshift-eng/ai-helpers/pre-commit-review)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/pre-commit-review"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/pre-commit-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/skills/openshift-eng/ai-helpers/pre-commit-review"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/pre-commit-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.00043 | $0.01327 |
| Opus 5.5 | $0.00017 | $0.00531 |
| Sonnet 5.5 | $0.00009 | $0.00265 |
| Haiku 4.5 | $0.00004 | $0.00133 |
Grade A, and why
pre-commit-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 21d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
code-review:pre-commit-review
Synopsis
/code-review:pre-commit-review [--language <lang>] [--profile <name>] [--skip-build] [--skip-tests]
Purpose
Review the current staged and unstaged changes before committing. Assess test coverage, idiomatic code, duplication, design, and build verification. Review only the current diff; do not report pre-existing issues in unchanged code.
The same-named skill replaces the former plugin command, so the /code-review:pre-commit-review invocation remains available in Claude Code. Install the plugin through APM to expose this skill to OpenCode and other supported clients.
Workflow
1. Resolve options and review guidance
Read options from the skill invocation or the user's request:
| Option | Behavior |
|---|---|
--language <lang> |
Apply language-specific review guidance. If omitted, detect from changed-file extensions. |
--profile <name> |
Apply project-specific conventions and checks. |
--skip-build |
Skip build verification and report it as skipped. |
--skip-tests |
Skip unit-test coverage review and report it as skipped. |
Detect the primary language from changed-file extensions: .go → Go, .py → Python, .rs → Rust, .ts/.tsx → TypeScript, and .java → Java. If files are mixed or the language has no guidance, continue with a general review.
Load optional guidance from sibling skill directories, relative to this SKILL.md:
- Language:
../<language>-code-review/SKILL.md(currently available:../go-code-review/SKILL.md). - Profile:
../<name>-code-review/SKILL.md(for example,../hypershift-code-review/SKILL.md).
If requested guidance is absent, say so and continue without it. Give loaded guidance to each relevant review pass.
Completion criterion: all supplied options are accounted for, and each available language/profile guide has been loaded before reviewing.
2. Establish the diff
Collect and deduplicate changed paths from both git diff --name-only and git diff --cached --name-only. Categorize them as source, tests, configuration, or documentation. If the diff is empty, report that and stop. If no source files changed, narrow the review accordingly.
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.
- 21d ago First seen · 104 lines · 43 tokens per session scan A 96f6594bc54b
pre-commit-review is a skill published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 1,327 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-01.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.