template-firm-setup

template-firm-setup is a command for Claude Code from llamadrive/bengo-toolkit. It costs 30 tokens per session (1,262 once invoked), scanned A, original, MIT.

A command for choosing the local folder used for templates shared across a firm. The folder must already be synchronized by software such as Google Drive, Dropbox, OneDrive, or an internal network drive.

In plain words
What is it for?
Use it to set or remove the shared template directory, verify that the folder exists, and let the plugin read and write templates through the computer’s existing sync setup.
Why use it?
It gives everyone a consistent template location without making the plugin upload files to a cloud service itself.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the bengo-toolkit plugin — 15 skills, 25 commands, 3 MCP servers shipped together

Install

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.

agentmods
npx agentmods add commands/llamadrive/bengo-toolkit/template-firm-setup
Clone the repo
git clone --depth 1 https://github.com/llamadrive/bengo-toolkit

Made for: Claude Code.

Or install bengo-toolkit, the plugin that ships this one along with the rest of its 15 skills, 25 commands, 3 MCP servers.

Wrote 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.

agentmods badge for template-firm-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/template-firm-setup.svg)](https://agentmods.dev/commands/llamadrive/bengo-toolkit/template-firm-setup)
Your own site
<a href="https://agentmods.dev/commands/llamadrive/bengo-toolkit/template-firm-setup"><img src="https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/template-firm-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.01262
Opus 5 $0.00015 $0.00631
Sonnet 5 $0.00006 $0.00252
Haiku 4.5 $0.00003 $0.00126

Measured 5d ago against content hash 5ec260138c41, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

template-firm-setup 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 5d 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.

commands/template-firm-setup.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

事務所全員で共有するテンプレートディレクトリのローカルパスを設定する。本プラグインは クラウドサービスに直接アップロードしない。設定されたローカルディレクトリを読み書きする だけで、実体の同期はあなたの PC 上で動いている同期アプリ(Google Drive / Dropbox / OneDrive / 社内 SMB マウント等)が担当する。

$ARGUMENTS:

  • パス(必須、--unset を除く)— クラウド同期アプリが PC 上にマウントしているローカルディレクトリ
  • --unset — 既存設定を削除する

Step 0: 動作環境ガード

Bash: python3 skills/_lib/workspace.py check --require local_fs
  • exit 0 → 次の Step へ進む
  • exit 2 → stdout の日本語メッセージをそのままユーザーへ表示して停止
  • exit 1 → stderr の error JSON をユーザーに伝えて停止

典型的なセットアップ

事務所の管理担当が一度だけ:

  1. Google Shared Drive(または社内 SMB / Dropbox 共有フォルダ)に 事務所/法人テンプレート/ のようなフォルダを作る
  2. 事務所メンバー全員にアクセス権を付与
  3. 各メンバーが自分の PC で同期アプリを起動し、フォルダがローカルにマウント されることを確認(macOS なら ~/Library/CloudStorage/GoogleDrive-.../Shared drives/...

各メンバーが一度だけ:

/template-firm-setup ~/Library/CloudStorage/[email protected]/Shared\ drives/事務所/法人テンプレート

ワークフロー

Step 1: パス検証 + 設定書込

python3 skills/_lib/workspace.py firm-setup "<absolute path>"

戻り値 JSON:

{
  "ok": true,
  "firm_templates_path": "/path/to/folder",
  "readme_created": true,
  "message": "firm スコープを ... に設定した。"
}

エラーケース(exit 1):

  • パスが存在しない → 「クラウド同期アプリが起動していて、フォルダが PC 上にマウントされているか確認してほしい」と案内
  • ディレクトリではない(ファイル等)→ 「ファイルではなくフォルダを指定してほしい」と案内
  • ~/.claude-bengo/ 配下を指定 → 「「この PC の全案件で共通」の領域と混線するので不可」と案内

Step 2: 完了案内

設定成功後、以下を案内する:

「事務所共有」の保存フォルダを設定した: {path}

以降:
  /template-list                       — 全保存場所のテンプレートを一覧
  /template-create --scope firm        — このフォルダに新規テンプレートを登録(個人情報検出時は拒否)
  /template-install <id> --scope firm  — 同梱書式を「事務所共有」にインストール
  /template-promote <id> --to firm     — この案件のみ → 事務所共有 へ移動(管理担当向け)
  /template-demote <id> --from firm    — 事務所共有 → この案件のみ にコピー(特定案件だけカスタマイズ)

注意: このフォルダにはクライアントの個人情報を含むファイルを置かないこと。事務所全員から見える。
個人情報のスキャンは移動・保存時に自動的にかかる(検出時は拒否)。

Step 3: 設定削除(--unset

python3 skills/_lib/workspace.py firm-setup --unset

戻り値:

{"unset": true, "message": "firm スコープ設定を削除した。"}

削除後は「事務所共有」が未設定状態に戻り、テンプレート解決は「この案件のみ」と 「この PC の全案件で共通」の 2 つだけになる。

Read the full file on GitHub · 112 lines

Changes

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.

  1. 5d ago First seen · 112 lines · 30 tokens per session scan A 5ec260138c41

Subscribe to this mod's changes

template-firm-setup is a command published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,262 once invoked, about $0.0002 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.