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/bacchus-labs/wrangler/init-workspacegit clone --depth 1 https://github.com/bacchus-labs/wranglerWrote 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/bacchus-labs/wrangler/init-workspace)<a href="https://agentmods.dev/commands/bacchus-labs/wrangler/init-workspace"><img src="https://agentmods.dev/badge/commands/bacchus-labs/wrangler/init-workspace.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.00012 | $0.00881 |
| Opus 5 | $0.00006 | $0.00441 |
| Sonnet 5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
init-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 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.
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.
/wrangler:init-workspace
Initialize or verify the .wrangler/ workspace directory structure using the init_workspace MCP tool. Idempotent -- safe to run repeatedly.
Arguments
--fix(optional) -- Apply changes. Without this flag, runs in report-only mode showing what would be created.--project-root=<path>(optional) -- Override project root directory. Defaults to git root or cwd.
What This Tool Does
The init_workspace MCP tool is the schema-driven workspace initializer. It:
- Creates directories defined in
workspace-schema.jsonusing mkdir -p semantics (idempotent) - Provisions builtin assets -- copies agent definitions, prompt templates, and workflow YAML files into
.wrangler/orchestration/subdirectories, skipping any file that already exists at the destination (never overwrites user customizations) - Generates config -- creates
.wrangler/config/wrangler.jsonwith project defaults if it doesn't exist - Manages .gitignore -- appends missing patterns from the schema without duplicating existing entries
- Updates schema -- copies
workspace-schema.jsonto the project if the plugin has a newer version
Modes
Report-Only (default, fix: false)
Shows what would be created without making any changes. Use this to audit workspace state.
init_workspace {}
Returns status: compliant (everything exists) or changes_needed (with details of what's missing).
Apply (fix: true)
Creates all missing directories, copies missing assets, generates config, updates gitignore.
init_workspace { "fix": true }
Returns status: initialized (changes were made) or compliant (nothing to do).
Instructions
- Call the
init_workspaceMCP tool with the appropriate parameters - Review the structured result showing directories, assets, config, and gitignore status
- Report findings to the user
Report-only mode (no --fix flag):
init_workspace({})
// or with explicit project root:
init_workspace({ projectRoot: "/path/to/project" })
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 · 102 lines · 12 tokens per session scan A 77dcf665faa2
init-workspace is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 881 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.