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/template-listgit 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/template-list)<a href="https://agentmods.dev/commands/llamadrive/bengo-toolkit/template-list"><img src="https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/template-list.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.00024 | $0.01487 |
| Opus 5 | $0.00012 | $0.00744 |
| Sonnet 5 | $0.00005 | $0.00297 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
template-list 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
「この PC の全案件で共通」(~/.claude-bengo/templates/)、「事務所共有」
(/template-firm-setup で設定したフォルダ)、「この案件のみ」(現在の案件
フォルダの .claude-bengo/templates/)に登録されているテンプレートを一覧表示する。
Step 0: 動作環境ガード
Bash: python3 skills/_lib/workspace.py check --require local_fs
- exit 0 → Step 1 へ
- exit 2 → stdout の日本語メッセージをそのままユーザーへ表示して停止
- exit 1 → stderr の error JSON をユーザーに伝えて停止
Step 1: 全保存場所の一覧取得
python3 skills/_lib/workspace.py templates
戻り値の JSON:
{
"workspace_root": "...",
"case_templates_dir": "...",
"firm_templates_dir": "..." | null,
"firm_status": "unconfigured" | "unreachable" | "reachable",
"user_templates_dir": "...",
"case": [{ "id": "...", "broken": false,
"shadowed_user": false, "shadowed_firm": false }, ...],
"firm": [{ "id": "...", "broken": false, "shadowed": false }, ...],
"user": [{ "id": "...", "broken": false, "shadowed": false }, ...]
}
firm_status:
unconfigured— 未設定。/template-firm-setupを案内するunreachable— 設定済みだがランタイムでパスが見つからない(同期クライアント停止等)reachable— 正常
broken エントリの扱い: broken: true のエントリは yaml または xlsx が
欠落している半端な状態。/template-fill では使えないが、表示からは隠さない
(silently 隠すと「登録したはずなのに一覧にない」とユーザーが混乱する)。
該当行には ⚠ {missing} ファイルが欠落 を併記する。
Step 2: 各 YAML を Read で読み取りメタデータを取得
各エントリの yaml_path を Read で開き、title / category / fields の数を取得する。
Step 3: 表示
以下の形式で表示する(「この案件のみ」を上、「事務所共有」を中、「この PC の全案件で共通」を下):
案件 '{案件フォルダ名}' で利用可能なテンプレート:
[この案件のみ] {case_templates_dir}
1. {title}(カテゴリ: {category} / フィールド: {N}件) ⚠ 事務所版を上書き中
[事務所共有] {firm_templates_dir} [到達可]
2. {title}(カテゴリ: {category} / フィールド: {N}件) — この案件で上書き中
3. ...
[この PC の全案件で共通] {user_templates_dir}
4. {title}(カテゴリ: {category} / フィールド: {N}件)
5. ...
操作:
/template-fill — テンプレートにデータを入力する
/template-create — 新規登録(既定: この案件のみ)
/template-create --scope firm — 事務所共有に登録(個人情報検出時は自動拒否)
/template-create --scope user — この PC の全案件で共通に登録(個人情報検出時は自動拒否)
/template-install — 同梱書式をインストール(既定: この案件のみ)
/template-promote <id> --to firm — 案件→事務所共有へ移動(個人情報を自動チェック)
/template-demote <id> --from firm — 事務所共有→案件にコピー
/template-firm-setup — 事務所共有フォルダのローカルパスを 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.
- 3d ago First seen · 103 lines · 24 tokens per session scan A 75f11ab0c229
template-list is a command published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 1,487 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.