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/0xbeycan/genesis/review-own-diffnpx skills add 0xBeycan/genesis --skill review-own-diffgit clone --depth 1 https://github.com/0xBeycan/genesisWrote 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/0xbeycan/genesis/review-own-diff)<a href="https://agentmods.dev/skills/0xbeycan/genesis/review-own-diff"><img src="https://agentmods.dev/badge/skills/0xbeycan/genesis/review-own-diff.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.00050 | $0.00242 |
| Opus 5 | $0.00025 | $0.00121 |
| Sonnet 5 | $0.00010 | $0.00048 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
review-own-diff 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 6d 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
Review your own diff
When to use
After building, before calling anything complete — in either lane. This is the cheapest place to catch the problems the vibe lane tends to create.
Steps
- Read the actual diff (don't review from memory).
- Check against the Definition of Done (
docs/process/definition-of-done.md). - Check the golden rules: module boundaries intact? no secrets? repo language? contract exists before the code that needs it? comments explain "why"?
- If the change became load-bearing, escalate to the spec lane: write the
spec/ADR retroactively (see
write-adr). - Fix what you found, then run
wrap-session.
Notes
Be honest about findings — report what's still broken rather than smoothing over it. A failing check named out loud is worth more than a green claim.
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.
- 6d ago First seen · 27 lines · 50 tokens per session scan A 78d3c5f4dc54
review-own-diff is a skill published in the GitHub repository 0xBeycan/genesis (11 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 242 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-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.