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 agentmods add skills/chi-qhsun/codex-semantic-review/commit-reviewnpx skills add chi-qhsun/Codex-Semantic-Review --skill commit-reviewgit clone --depth 1 https://github.com/chi-qhsun/Codex-Semantic-ReviewWrote 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/chi-qhsun/codex-semantic-review/commit-review)<a href="https://agentmods.dev/skills/chi-qhsun/codex-semantic-review/commit-review"><img src="https://agentmods.dev/badge/skills/chi-qhsun/codex-semantic-review/commit-review.svg" alt="Measured on agentmods" 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.00060 | $0.00288 |
| Opus 5 | $0.00030 | $0.00144 |
| Sonnet 5 | $0.00012 | $0.00058 |
| Haiku 4.5 | $0.00006 | $0.00029 |
Grade A, and why
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 4d 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.
What it actually says
Commit Review
After the mandatory post-commit reminder, explicitly invoke the local
codex-commit-review MCP. Use prepare_commit_history_review and
create_commit_history_review for multiple pending SHAs; use the compatible
single-commit tools for one SHA. Keep committed parent-to-SHA diffs separate
from any dirty working tree.
Use stable plan item IDs when a build plan exists. When it does not, retain the
MCP's explicitly marked auto-generated / unplanned plan. Author substantive
before/after, contract, risk, and verification explanations for every required
file/function/block/line target and link them with plan_item_ids.
Require the localhost URL, root digest, per-commit receipts, important files,
plan coverage, four comment counters, and semantic_review.passed for every
requested SHA. Heuristic notes never satisfy the semantic gate. Amend/rebase
replacements use their new SHA; unreachable superseded commits are inactive.
This local workflow never authorizes push, merge, upload, or unrelated process
changes.
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.
- 4d ago First seen · 25 lines · 60 tokens per session scan A de19fbdc9745
commit-review is a skill published in the GitHub repository chi-qhsun/Codex-Semantic-Review (0 stars, last pushed 12d ago), licensed MIT. It adds 60 tokens to every session and 288 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…