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.5 | $0.00025 | $0.01493 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (112 stars, last pushed 23d ago), licensed MIT. It adds 63 tokens to every session and 3,733 once invoked, about $0.0003 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-03.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…
git-workflow
Branching and review conventions.
om-auto-fix-pr
Drive an open PR to merge-ready from its number — merges the latest base, then loops review-autofix (om-auto-review-pr), built-in CI stabilization, and UI verification (om-auto-qa-pr) until approvable, green, and QA-evidenced. A --ci-only mode drives just CI green on a PR or a plain branch. Files follow-up issues for…
om-approve-merge-pr
Approve (submit an approving review) and squash-merge a PR given only its number, refusing when the QA gate or a blocking label forbids it. Routes fixable blockers to om-auto-fix-pr (red CI via its --ci-only mode, or conflicts and review problems via the full loop). Optionally file a follow-up issue at the same time.…