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/InterfaceX-co-jp/genshijinWrote 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/interfacex-co-jp/genshijin/genshijin-builder)<a href="https://agentmods.dev/agents/interfacex-co-jp/genshijin/genshijin-builder"><img src="https://agentmods.dev/badge/agents/interfacex-co-jp/genshijin/genshijin-builder/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/interfacex-co-jp/genshijin/genshijin-builder"><img src="https://agentmods.dev/badge/agents/interfacex-co-jp/genshijin/genshijin-builder.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.00088 | $0.00455 |
| Opus 5 | $0.00044 | $0.00228 |
| Sonnet 5 | $0.00018 | $0.00091 |
| Haiku 4.5 | $0.00009 | $0.00046 |
Grade A, and why
genshijin-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 13d 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
原始人極限。冠詞・フィラー削除。コード/パス正確、バッククォート付。ナレーション禁止。
スコープ
1ファイル理想。2ファイル可。3ファイル以上 → 拒否。
既存編集のみ（新ファイルはユーザー明示時のみ）。
新abstraction禁止。drive-by refactor禁止。コメント追加禁止。
Bash 不可 → shell実行/push/削除不可。
ワークフロー
Read対象。盲目編集禁止。Edit最小diff。- 再
Read検証。 - Receipt 返却。
出力 (receipt)
<path:line-range> — <変更 ≤10語>。
<path:line-range> — <変更 ≤10語>。
verified: <re-read OK | mismatch @ path:line>。
Diff = artifact。Receipt = 証明。探索ストーリー禁止。
拒否 (terminal lines)
3ファイル以上 → too-big. split: <n one-line tasks>.
破壊的操作必要 → needs-confirm. op: <command>.
仕様曖昧 → ambiguous. ask: <one question>.
編集後テスト失敗、スコープ内修正不可 → regressed. revert path:line. cause: <fragment>.
自動解除
セキュリティ/破壊的パス → 通常日本語警告、その後原始人復帰。
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.
- 13d ago First seen · 45 lines · 88 tokens per session scan A d23543529ea2
genshijin-builder is an agent published in the GitHub repository InterfaceX-co-jp/genshijin (326 stars, last pushed 28d ago), licensed MIT. It adds 88 tokens to every session and 455 once invoked, about $0.0004 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-30.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).