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 commands/llamadrive/bengo-toolkit/case-infogit clone --depth 1 https://github.com/llamadrive/bengo-toolkitWrote 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/commands/llamadrive/bengo-toolkit/case-info)<a href="https://agentmods.dev/commands/llamadrive/bengo-toolkit/case-info"><img src="https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/case-info.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.00011 | $0.00891 |
| Opus 5 | $0.00005 | $0.00445 |
| Sonnet 5 | $0.00002 | $0.00178 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
case-info 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 3d 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
現在のフォルダ(または指定フォルダ)の案件状態を要約する。bengo-toolkit
は案件フォルダごとに .claude-bengo/ を持つ(ディレクトリ名は v3.7.0 でのリネーム
時にも互換性のため据え置き)。このコマンドはその中身を読み、
監査ログの件数・テンプレート数・メタデータを可視化する。
$ARGUMENTS
- 引数なし: 現在の案件フォルダを対象に
--verify: 改ざん検知ログ(ハッシュチェーン)の整合性も併せて検証する
Step 0: 動作環境ガード
Bash: python3 skills/_lib/workspace.py check --require local_fs
- exit 0 → 次の Step へ進む
- exit 2 → stdout の日本語メッセージをそのままユーザーへ表示して停止
- exit 1 → stderr の error JSON をユーザーに伝えて停止
動作
Step 1: 案件フォルダ解決
python3 skills/_lib/workspace.py info
未初期化の場合は以下を表示:
このフォルダ(~/cases/new-case)は bengo-toolkit の案件フォルダとして
初期化されていない。機密スキル(/typo-check, /family-tree 等)を実行すると
自動的に `.claude-bengo/` が作成される。事前登録したい場合:
python3 skills/_lib/workspace.py init
Step 2: 情報表示
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
案件: smith-v-jones
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
フォルダ: ~/cases/smith-v-jones
開始日: 2026-04-10
最終更新: 2026-04-19 14:30 (2時間前)
監査ログ: ~/cases/smith-v-jones/.claude-bengo/audit.jsonl
件数: 127
直近イベント:
- 2026-04-19 14:30: family-tree file_write (family_tree_2026-04-19.html)
- 2026-04-19 14:28: family-tree file_read (戸籍.pdf)
- 2026-04-19 10:15: typo-check file_write (訴状_reviewed.docx)
- 2026-04-19 10:10: typo-check file_read (訴状.docx)
テンプレート(3 件):
- 財産目録
- 遺産分割協議書
- 陳述書(原告)
設定: 既定(/audit-config で変更可)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Step 3: --verify 指定時
python3 skills/_lib/audit.py verify を実行し、結果を末尾に追加:
改ざん検知ログ(ハッシュチェーン)検証: OK
subtotal: ok=127, fail=0, legacy=0, total=127
fail > 0 なら赤字で表示し、弁護士に手動確認を促す。
避けること
- 監査ログの中身(filename 等)を一切表示しない — metadata のみ
- 設定変更の質問をしない(
/audit-configの領域) - 他の案件フォルダを勝手にスキャンしない
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.
- 3d ago First seen · 89 lines · 11 tokens per session scan A c8b1f5bb8c88
case-info is a command published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 891 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.