configure-template-workspace

configure-template-workspace is a command for Claude Code from OfficialBoomi/bc-integration. It costs 19 tokens per session (1,008 once invoked), scanned A, original, BSD-2-Clause.

A command for setting up a personal Boomi project template and creating a command that starts new workspaces from it.

In plain words
What is it for?
Use it to choose where a template is stored, copy the reference template there, and configure the workspace-starting command.
Why use it?
It removes repeated manual setup when creating Boomi workspaces.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions CLAUDE.md; names the AskUserQuestion tool.

Part of the bc-integration plugin — 1 skill, 3 commands, 1 agent shipped together

Good fit Use it to choose where a template is stored, copy the reference template there, and configure the workspace-starting command.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/officialboomi/bc-integration/configure-template-workspace
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.

Clone the repo
git clone --depth 1 https://github.com/OfficialBoomi/bc-integration

Made for: Claude Code.

Or install bc-integration, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 1 agent.

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 configure-template-workspace

README.md
[![agentmods](https://agentmods.dev/badge/commands/officialboomi/bc-integration/configure-template-workspace/github.svg)](https://agentmods.dev/commands/officialboomi/bc-integration/configure-template-workspace)
Your own site
<a href="https://agentmods.dev/commands/officialboomi/bc-integration/configure-template-workspace"><img src="https://agentmods.dev/badge/commands/officialboomi/bc-integration/configure-template-workspace/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.

agentmods 80×15 button for configure-template-workspace

Your own site · 80×15
<a href="https://agentmods.dev/commands/officialboomi/bc-integration/configure-template-workspace"><img src="https://agentmods.dev/badge/commands/officialboomi/bc-integration/configure-template-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 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,008 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00019 $0.01008
Opus 5 $0.00010 $0.00504
Sonnet 5 $0.00004 $0.00202
Haiku 4.5 $0.00002 $0.00101

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

Security

Grade A, and why

configure-template-workspace 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 10d 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/configure-template-workspace.md · 102 lines

How it starts

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

This command sets up the user's personal Boomi project template (referred to as the User Template throughout this doc) and generates the global /freshies command for spinning up new workspaces from it.

The steps below locate the plugin's Reference Template and copy it into the User Template workspace location the user specifies.

Workflow

Step 1: Get Template Location

Use the AskUserQuestion tool to ask where they'd like their new User Template folder:

Question: "Where would you like your Boomi template folder to be stored?" Header: "Template path" Options (in this order):

  1. Current directory - "Use this current working directory" - The directory they're running the command from
  2. ~/boomi-template - "Default location in your home directory"
  3. ~/Desktop/boomi-template - "On your Desktop for easy access"

The user can also select "Other" to provide a custom path.

Step 2: Find the Reference Template Directory

Work through this checklist:

  • Load the boomi-integration skill. The loader prints a line near the top of the output: Base directory for this skill: <install-path>/bc-integration/skills/boomi-integration.
  • Strip the trailing /skills/boomi-integration from the base directory → that's the plugin root.
  • Append /template to the plugin root → that's the Reference Template path.
  • Verify the path exists with ls <path> before proceeding.

Example: base dir ~/bc/plugins/bc-integration/skills/boomi-integration → Reference Template at ~/bc/plugins/bc-integration/template/.

If the skill fails to load (uncommon) or the template path doesn't exist, ask the user where the bc-integration plugin is installed.

We will call this resolved path PLUGIN_REFERENCE_TEMPLATE_DIR going forward.

Step 3: Copy Template to Workspace

If the new User Template workspace folder doesn't exist:

  • Create the User Template folder
  • Copy all contents from PLUGIN_REFERENCE_TEMPLATE_DIR/ to their chosen location
  • Inform them to set up .env with their credentials (copy from .env.example)

Read the full file on GitHub · 102 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. 10d ago First seen · 102 lines · 19 tokens per session scan A b89464c5f37f

Subscribe to this mod's changes

configure-template-workspace is a command published in the GitHub repository OfficialBoomi/bc-integration (12 stars, last pushed 10d ago), licensed BSD-2-Clause. It adds 19 tokens to every session and 1,008 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-30.