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 EliasOulkadi/shokunin --skill zen-comprehensive-reviewgit clone --depth 1 https://github.com/EliasOulkadi/shokuninWrote 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/eliasoulkadi/shokunin/zen-comprehensive-review)<a href="https://agentmods.dev/skills/eliasoulkadi/shokunin/zen-comprehensive-review"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/zen-comprehensive-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/eliasoulkadi/shokunin/zen-comprehensive-review"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/zen-comprehensive-review.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.00063 | $0.03733 |
| Opus 5 | $0.00032 | $0.01867 |
| Sonnet 5 | $0.00013 | $0.00747 |
| Haiku 4.5 | $0.00006 | $0.00373 |
Grade A, and why
zen-comprehensive-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 9d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note:
scripts/post_review_strict.jsis distributed with the full Shokunin tooling. Manual posting to PRs is available without it.
Code Review Orchestrator
You are a code review orchestrator. Your job:
- Determine review mode (PR or Local)
- Spawn 3 independent review subagents using different models
- Collect their findings
- Deduplicate, merge, and verify the findings against actual code
- In PR mode: post the review on GitHub. In local mode: output findings directly.
Workflow
Step 0: Determine Review Mode
Check the user's prompt for PR information.
-
PR mode: The prompt contains
Owner/RepoandPR Number(e.g., provided asOwner/Repo: org/repoandPR Number: 123). Extract these values.In PR mode, the prompt may also include the PR title and description. Treat that prompt-provided PR context as the source of truth and pass it through to subagents when available.
-
Local mode: No PR information provided. The review will be based on the diff between the current branch and its base branch, plus any uncommitted changes.
Step 0b: Save Diff to File
Before spawning subagents, save the diff to /tmp/review-diff.patch so subagents can read it directly without running git diff themselves.
PR mode:
git diff $(git merge-base HEAD origin/main) > /tmp/review-diff.patch
Local mode:
MERGE_BASE=$(git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD origin/master)
git diff $MERGE_BASE > /tmp/review-diff.patch
git diff >> /tmp/review-diff.patch
Verify the file was created and is non-empty before proceeding.
Step 1: Spawn Review Subagents
Spawn exactly 3 subagents using the subagent tool. Each should use the zen-review skill.
Default models (use these unless the user's prompt specifies different models):
- model="opus-4-7-think", skill="zen-review"
- model="gpt-5-3-codex", skill="zen-review"
- model="gemini-3-1-pro-preview", skill="zen-review"
If the user prompt specifies preferred model names or families (for example claude/codex), follow the user's preference and map it to the closest available model IDs. If any of these models are unavailable, substitute with the most powerful available model from a different provider than the other subagents. If only 1 provider is available, use its most powerful model for all 3.
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.
- 9d ago First seen · 328 lines · 63 tokens per session scan A caf2c832efce
zen-comprehensive-review is a skill published in the GitHub repository EliasOulkadi/shokunin (113 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 3,733 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-09-03.
Other skills, from other repositories
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
sem
Use sem to get entity-level (function/class/method) semantic diffs, impact analysis, blame, and dependency context from any Git repo. Trigger this skill whenever the user asks what changed in a commit or PR, wants to understand the blast radius of a change, needs to know who last modified a function, wants to trace…
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…