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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/bootstrap)<a href="https://agentmods.dev/commands/travisjneuman/.claude/bootstrap"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/bootstrap.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.1 | $0.00000 | $0.01288 |
| Opus 5 | $0.00000 | $0.00644 |
| Sonnet 5 | $0.00000 | $0.00258 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
bootstrap 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap - System Configuration & Verification
Verifies and repairs the Claude Code Toolkit installation.
Use cases:
- Fresh install verification (after running install.sh)
- Troubleshooting configuration issues
- Ensuring cross-machine sync is working
- Repairing broken submodule configurations
Execution Protocol
Step 1: System Information
Report the current environment:
echo "Platform: $(uname -s)"
echo "Shell: $SHELL"
echo "Claude Dir: $HOME/.claude"
echo "Git version: $(git --version)"
echo "Node version: $(node --version)"
Step 2: Core Files Verification
Check that essential files exist:
| File | Purpose | Required |
|---|---|---|
CLAUDE.md |
Core rules and configuration | ✓ |
settings.json |
Permissions, hooks, plugins | ✓ |
scripts/hooks/session-start.sh |
Auto-routing injection | ✓ |
.mcp.json |
MCP server configuration | ✓ (platform-specific) |
Action: Read and verify each file exists. If missing, report which files need attention.
Step 3: Submodule Health Check
Verify all marketplace repos are properly configured:
cd ~/.claude
# Check submodule status
git submodule status
# Verify no_push on all marketplace repos
for repo in plugins/marketplaces/*/; do
push_url=$(cd "$repo" && git remote get-url --push origin 2>/dev/null)
if [ "$push_url" != "no_push" ]; then
echo "FIX NEEDED: $repo needs no_push configured"
fi
done
If issues found: Offer to fix automatically:
# Fix no_push for all marketplace repos
for repo in ~/.claude/plugins/marketplaces/*/; do
(cd "$repo" && git remote set-url --push origin no_push)
done
Step 4: Hook Verification
Check that hooks are properly configured:
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 · 240 lines · 0 tokens per session scan E d2e33815f4f2
bootstrap is a command published in the GitHub repository travisjneuman/.claude (96 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,288 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-09-03.
Other commands, from other repositories
performance-audit
Find performance bottlenecks across the stack — queries, rendering, bundle size, memory.
debug
Systematic debugging — reproduce, isolate, fix, verify, and add regression test.
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.
build-fix
A build-error fixing procedure for TypeScript projects. It runs the project build, groups and explains errors, applies fixes one at a time, and checks the build again.
gates-csk
Gate report — what the tool-level gates actually did, and which rules nothing has tripped.
refactor-cleanup.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.