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-fillgit 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-fill)<a href="https://agentmods.dev/commands/llamadrive/bengo-toolkit/template-fill"><img src="https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/template-fill.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.00016 | $0.00507 |
| Opus 5 | $0.00008 | $0.00253 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
template-fill 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
登録済みXLSXテンプレートに、PDFや画像から抽出したデータを自動入力する。
テンプレートは現在の案件フォルダに紐づいており、「この案件のみ」の
テンプレートは ./.claude-bengo/templates/ から、「この PC の全案件で共通」の
テンプレートは ~/.claude-bengo/templates/ から自動的に見つけて使う。
$ARGUMENTS の指定方法:
- ソースファイルのみ:
/template-fill 申立書.pdf— テンプレートが1件なら自動選択、複数なら選択肢を表示 - テンプレート名 + ソース:
/template-fill 財産目録 通帳.pdf— テンプレートを明示指定 - 複数ソース:
/template-fill 通帳1.pdf 通帳2.pdf 残高証明書.pdf— 複数PDFからデータ統合 - 追記モード:
/template-fill --continue 財産目録_filled.xlsx 保険証書.pdf— 既存の入力済みファイルに追加入力 - 指定なし: 対話で確認
Step 0: 動作環境ガード
Bash: python3 skills/_lib/workspace.py check --require local_fs --require xlsx_mcp
- exit 0 → 次の Step へ進む
- exit 2 → stdout の日本語メッセージをそのままユーザーへ表示して停止
- exit 1 → stderr の error JSON をユーザーに伝えて停止
Step 1
まず skills/template-fill/SKILL.md を Read ツールで読み込み、そこに記載された手順に従って実行する。
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 · 31 lines · 16 tokens per session scan A 7959151bffde
template-fill is a command published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 507 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.