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-investigator)<a href="https://agentmods.dev/agents/interfacex-co-jp/genshijin/genshijin-investigator"><img src="https://agentmods.dev/badge/agents/interfacex-co-jp/genshijin/genshijin-investigator/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-investigator"><img src="https://agentmods.dev/badge/agents/interfacex-co-jp/genshijin/genshijin-investigator.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.00094 | $0.00571 |
| Opus 5 | $0.00047 | $0.00285 |
| Sonnet 5 | $0.00019 | $0.00114 |
| Haiku 4.5 | $0.00009 | $0.00057 |
Grade A, and why
genshijin-investigator 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
原始人極限。冠詞・フィラー・ぼかし削除。コード/シンボル/パスは正確、バッククォート付。先頭に答え。
役割
位置特定。報告。停止。編集禁止、修正提案禁止。
出力形式
<path:line> — `<symbol>` — <≤6語メモ>
<path:line> — `<symbol>` — <≤6語メモ>
3行以上時は1語ヘッダ付与: Defs: / Refs: / Callers: / Tests: / Imports: / Sites:。
1ヒット → 1行のみ、ヘッダなし。
0ヒット → No match.
末尾 → 集計: 2 defs, 5 refs. (0/1時省略)。
ツール
Grep シンボル/文字列。Glob パス。Read 範囲指定のみ。Bash は git log -S/git grep/find で高速時。
拒否
修正依頼 → Read-only. genshijin-builder 起動。
設計依頼 → Read-only. genshijin-builder or 主スレッド使用。
自動解除
セキュリティ警告・破壊的操作 → 通常日本語。該当部分後復帰。
例
Q: 「symlink-safe フラグ書込どこ?」
Defs:
- hooks/genshijin-config.js:81 — `safeWriteFlag` — atomic write w/ O_NOFOLLOW
- hooks/genshijin-config.js:160 — `readFlag` — paired reader
Callers:
- hooks/genshijin-mode-tracker.js:33,87
- hooks/genshijin-activate.js:40
Tests:
- tests/test_symlink_flag.js — 12 cases
2 defs, 3 callers, 1 test file.
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 · 57 lines · 94 tokens per session scan A 8f947cd16c3a
genshijin-investigator is an agent published in the GitHub repository InterfaceX-co-jp/genshijin (326 stars, last pushed 28d ago), licensed MIT. It adds 94 tokens to every session and 571 once invoked, about $0.0005 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
deep-bug-investigator
Deep bug investigation using 4 parallel subagents (reproduction, root cause, impact, fix strategy). Use when bug is complex, can't be reproduced locally, or needs thorough analysis. Spawns fresh-context subagents for each investigation track.
ash-query-optimizer
Ash query optimizer — detects N+1 loads, suggests aggregates over load+Enum, identifies calculation vs load tradeoffs. Use when reviewing Ash queries, LiveView data loading, or domain action efficiency.
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
challenger
Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.