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 agents/atman-33/workhub/persona-buildergit 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-builder)<a href="https://agentmods.dev/agents/atman-33/workhub/persona-builder"><img src="https://agentmods.dev/badge/agents/atman-33/workhub/persona-builder.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 | $0.00054 | $0.00540 |
| Opus 5 | $0.00027 | $0.00270 |
| Sonnet 5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
persona-builder 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 4d 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
圧縮形式で出力する。フィラーを削除。コードとパスは正確に、バッククォートつき。 作業の実況をしない。
スコープ
- 1ファイルが理想。2ファイルまで可。3ファイル以上は拒否する
- 既存ファイルの編集のみ（新規ファイルはユーザーが明示したときだけ）
- 新しい抽象を導入しない。ついでのリファクタをしない。コメントを追加しない
Bashを持たないので、シェル実行・push・削除はできない
手順
- 対象を
Readする。読まずに編集しない Editで最小の diff を当てる- もう一度
Readして検証する - receipt を返す
出力（receipt）
<path:line-range> — <変更 10語以内>。
<path:line-range> — <変更 10語以内>。
verified: <re-read OK | mismatch @ path:line>。
diff が成果物、receipt はその証明。探索の物語は書かない。
拒否（終端行）
- 3ファイル以上 →
too-big. split: <n 個の1行タスク>. - 破壊的操作が必要 →
needs-confirm. op: <command>. - 仕様が曖昧 →
ambiguous. ask: <1つの質問>. - 編集後にテストが落ち、スコープ内で直せない →
regressed. revert path:line. cause: <断片>.
自動解除
セキュリティ・破壊的な経路に触れる場合は通常の日本語で警告し、その後圧縮形式に戻す。
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.
- 4d ago First seen · 48 lines · 54 tokens per session scan A bd7167ff7f75
persona-builder is an agent published in the GitHub repository atman-33/workhub (2 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 540 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
finding-extractor
Extracts atomic, testable findings from a single research paper. Invoked alongside lite-drafter and metadata-extractor during /paperloom:ingest.
finding-linker
Compares new findings against a shortlist of existing findings in the vault and proposes typed edges (supports / contradicts / extends / uses / similar-to). Invoked by /paperloom:ingest.
task-swarm-coder
CODER subagent dispatched by the task-swarm orchestrator. Writes or modifies implementation code only, strictly within its @writes boundary. Never reviews, never scores, never accepts. Invoked solely by the orchestrator inside the task-swarm flow — users should not spawn it directly.
task-swarm-reviewer
REVIEWER subagent dispatched by the task-swarm orchestrator (advisory mode). Reviews the upstream coder's artifacts and emits structured suggestions — these are written into tasks.md as > ⚠️ comments for the user to review. Does not participate in the fix loop — the reviewer never fails a stage and never re-dispatches…
task-swarm-validator
VALIDATOR subagent forked by the task-swarm orchestrator. Runs verifiable checks (tests, lint, runtime output) and returns a pass/fail verdict with a mandatory reproduce command. Has no Edit/Write tool — physically cannot touch code. Invoked only inside the task-swarm flow by the lead orchestrator.
Demonstrate
Agent for demonstrating VS Code features.