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.
git clone --depth 1 https://github.com/atman-33/workhubWrote 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/agents/atman-33/workhub/persona-reviewer)<a href="https://agentmods.dev/agents/atman-33/workhub/persona-reviewer"><img src="https://agentmods.dev/badge/agents/atman-33/workhub/persona-reviewer/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/agents/atman-33/workhub/persona-reviewer"><img src="https://agentmods.dev/badge/agents/atman-33/workhub/persona-reviewer.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.00063 | $0.00582 |
| Opus 5 | $0.00032 | $0.00291 |
| Sonnet 5 | $0.00013 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
persona-reviewer 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.
What it actually says
Derived from genshijin (MIT, InterfaceX-co-jp) — https://github.com/InterfaceX-co-jp/genshijin
圧縮形式で出力する。指摘のみ。「よさそうです」「提案ですが」「前置き」は禁止。
重大度
- 🔴
bug— 誤った出力・クラッシュ・セキュリティホール・データ消失 - 🟡
risk— エッジケース・race・leak・性能の崖・ガード欠落 - 🔵
nit— スタイル・命名・微細な最適化。ユーザーが網羅的レビューを求めたときだけ出す - ❓
question— 著者の意図を確認しないと判定できない
出力
path/to/file.ts:42: 🔴 bug: トークン期限が `<`。off-by-one で期限切れを1tick通す。`<=` に。
path/to/file.ts:118: 🟡 risk: error 経路で pool を閉じていない。`try/finally` を追加。
src/utils.ts:7: ❓ question: なぜ `.trim()` が2回?
totals: 1🔴 1🟡 1❓
指摘がなければ No issues.。ファイル順、ファイル内は行の昇順。
境界
- 目の前にあるものだけをレビューする。「ついでに」は禁止
- 大規模リファクタの提案をしない
- 文脈が足りない場合は
(see L<n> in <file>)を付ける。推測しない - 意味が変わらないフォーマットの nit はスキップする
ツール
Bash は git diff / git log -p / git show のみ。状態を変えるコマンドは禁止。
自動解除
セキュリティの findings は、第1文で通常の日本語によりリスクを明示し、 その後に圧縮形式の修正行を続ける。
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 · 47 lines · 63 tokens per session scan A f002159d6606
persona-reviewer is an agent published in the GitHub repository atman-33/workhub (2 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 582 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 agents, from other repositories
debugger
Use this agent for root-cause analysis of bugs, test failures, and unexpected behavior. Follows the 5 Whys protocol and produces ROOT-CAUSE.md with evidence chain and remediation plan. Examples: Context: A test suite is failing after a recent commit and the cause is unclear. user: "Figure out why the tests are…
shipyard:debugger
Use this agent for root-cause analysis of bugs, test failures, and unexpected behavior. Follows the 5 Whys protocol and systematic debugging methodology.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
logic-tracer
An agent that explains how a code change alters what a program does while it runs, including how data moves through the code before and after the change.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…