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 Unique-Divine/jiyuu --skill gh-revgit clone --depth 1 https://github.com/Unique-Divine/jiyuuWrote 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/unique-divine/jiyuu/gh-rev)<a href="https://agentmods.dev/skills/unique-divine/jiyuu/gh-rev"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/gh-rev/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/unique-divine/jiyuu/gh-rev"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/gh-rev.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.00119 | $0.01032 |
| Opus 5.5 | $0.00048 | $0.00413 |
| Sonnet 5.5 | $0.00024 | $0.00206 |
| Haiku 4.5 | $0.00012 | $0.00103 |
Grade A, and why
gh-rev 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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gh-rev
Use gh-rev as the durable workflow and identity layer around code review.
It records Markdown revisions outside source repositories, normally under
~/gh. Use gh-pr-review alongside it whenever judging code: that skill owns
review depth, categories, evidence, and the final recommendation. This skill
owns target selection, history, revision allocation, and finding lifecycle.
Choose the workflow
Read only the reference matching the user's task:
- "Review my current branch with gh-rev; it is not a PR yet." Read references/review-local-branch.md.
- "Review the published PR for this branch" or "Review PR #1153." Read references/review-pull-request.md.
- "Are there unresolved reviews?", "What feedback remains?", or "Resolve this finding after verification." Read references/work-revisions.md.
- "Implement the submitted reviews," "Address the review feedback," or "Automatically fix clear findings while implementing this slice." Read references/implement-review-feedback.md.
- For another independent review pass, use the applicable local-branch or PR reference. A new pass receives a new revision; addressing an existing pass does not.
If a local branch is associated with a PR, select the authority that matches the user's intent:
- Review what is published on GitHub with
--pr. - Review unpublished local commits with
--branch ... --head localwhen that option is supported.
Do not silently substitute one for the other when their heads diverge.
Start with capability and context
Run command -v gh-rev and inspect gh-rev --help before choosing commands.
The installed binary can lag the source documentation. Use sync, --pr, and
--head local only when help advertises them. Prefer the current command
contract when present; follow the compatibility behavior in the relevant
reference otherwise.
What ships with it
4 files 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.
- 1mo ago First seen · 96 lines · 119 tokens per session scan A 122cc236e7c2
gh-rev is a skill published in the GitHub repository Unique-Divine/jiyuu (6 stars, last pushed 8d ago), licensed MIT. It adds 119 tokens to every session and 1,032 once invoked, about $0.0005 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-08.
Other skills, from other repositories
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
bmad-loop
Iterate over a list of story keys, executing dev → review → PR → CI → merge for each. Use when the user says "loop these stories [list]" or "run the loop on [story keys]".
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
design-review
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.
agents-md
Generate AGENTS.md files for Go, Rust, TypeScript, and Java projects. Use this skill whenever the user asks to create, scaffold, bootstrap, update, or review an AGENTS.md (or agent-instructions, CLAUDE.md, repo guide for agents) file in a codebase. Also trigger when the user says "add AGENTS.md", "make this repo…
skill-creator
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory.