Borrowing it
Nothing to install: this file belongs to zhangreling02-ai/3dslicer-claude-bridge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zhangreling02-ai/3dslicer-claude-bridge/main/.claude/commands/bootstrap-env.mdgit clone --depth 1 https://github.com/zhangreling02-ai/3dslicer-claude-bridgeWrote 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/zhangreling02-ai/3dslicer-claude-bridge/bootstrap-env)<a href="https://agentmods.dev/commands/zhangreling02-ai/3dslicer-claude-bridge/bootstrap-env"><img src="https://agentmods.dev/badge/commands/zhangreling02-ai/3dslicer-claude-bridge/bootstrap-env/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.
<a href="https://agentmods.dev/commands/zhangreling02-ai/3dslicer-claude-bridge/bootstrap-env"><img src="https://agentmods.dev/badge/commands/zhangreling02-ai/3dslicer-claude-bridge/bootstrap-env.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00679 |
| Opus 5 | $0.00000 | $0.00340 |
| Sonnet 5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
bootstrap-env 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bootstrap-env - Setup Claude Code Environment
Bootstrap your Claude Code environment with required plugins and configuration.
Description
This command helps you replicate a fully-configured Claude Code environment on any device or remote environment (like "Vibing"). It lists all the plugins that need to be installed and provides step-by-step guidance.
Usage
/bootstrap-env # Full setup guide
/bootstrap-env plugins # Just list plugins to install
/bootstrap-env verify # Check what's missing
Instructions
When the user invokes this command:
1. Show Environment Status
First, display what's currently available:
📋 Claude Code Environment Bootstrap
Current environment:
- Platform: [detect from system]
- Project: NC_Slicer-Claude-Bridge
2. List Required Plugins (23 total)
Display the plugins grouped by category:
Core Development:
/plugin install context7
/plugin install feature-dev
/plugin install code-review
/plugin install commit-commands
/plugin install pr-review-toolkit
/plugin install plugin-dev
Output Styles:
/plugin install explanatory-output-style
/plugin install learning-output-style
Integrations:
/plugin install greptile
/plugin install supabase
/plugin install figma
/plugin install slack
Language Support:
/plugin install typescript-lsp
/plugin install pyright-lsp
/plugin install rust-analyzer-lsp
/plugin install jdtls-lsp
Testing & Quality:
/plugin install playwright
/plugin install security-guidance
/plugin install agent-sdk-dev
/plugin install hookify
Specialized:
/plugin install frontend-design
/plugin install serena
/plugin install ralph-wiggum
/plugin install ralph-loop
3. If $ARGUMENTS is "plugins"
Just output the plugin install commands as a copyable block:
# Core
/plugin install context7 feature-dev code-review commit-commands pr-review-toolkit plugin-dev
# Styles
/plugin install explanatory-output-style learning-output-style
# Integrations
/plugin install greptile supabase figma slack
# Languages
/plugin install typescript-lsp pyright-lsp rust-analyzer-lsp jdtls-lsp
# Testing
/plugin install playwright security-guidance agent-sdk-dev hookify
# Specialized
/plugin install frontend-design serena ralph-wiggum ralph-loop
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.
- 10d ago First seen · 132 lines · 0 tokens per session scan A 6b77460138ff
bootstrap-env is a command published in the GitHub repository zhangreling02-ai/3dslicer-claude-bridge (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 679 tokens. 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.