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/b33eep/claude-code-setupWrote 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/b33eep/claude-code-setup/claude-code-setup)<a href="https://agentmods.dev/commands/b33eep/claude-code-setup/claude-code-setup"><img src="https://agentmods.dev/badge/commands/b33eep/claude-code-setup/claude-code-setup/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/b33eep/claude-code-setup/claude-code-setup"><img src="https://agentmods.dev/badge/commands/b33eep/claude-code-setup/claude-code-setup.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.03235 |
| Opus 5.5 | $0.00000 | $0.01294 |
| Sonnet 5.5 | $0.00000 | $0.00647 |
| Haiku 4.5 | $0.00000 | $0.00324 |
Grade A, and why
claude-code-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 1mo 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Setup
Manage your claude-code-setup installation: check status, upgrade, install, and remove modules.
Goal: Any scenario completes in 2 permission prompts (1 discover + 1 execute).
Phase 1: Discovery (1 Bash call)
Clone repo and run setup-status.sh in a single Bash call:
temp=$(mktemp -d /tmp/claude-setup-XXXXXX) && \
git clone --depth 1 https://github.com/b33eep/claude-code-setup.git "$temp" 2>/dev/null && \
"$temp/lib/setup-status.sh"
The script reads installed.json and templates/VERSION, compares modules, and outputs JSON.
Parse the JSON output. Handle errors:
-
Bash call fails (no network, git clone fails):
Unable to reach GitHub. Manual upgrade: cd /path/to/claude-code-setup git pull ./install.sh --updateStop here.
-
JSON has
"error": "not_installed"(no installed.json):claude-code-setup is not installed. Run install.sh first.Clean up:
rm -rf "$temp"→ Stop. -
Success: Parse JSON fields. The
temp_dirfield contains the repo path. Continue to Phase 2.
JSON structure reference
{
"temp_dir": "/tmp/claude-setup-XXXXXX",
"base": { "installed": 50, "available": 52, "update_available": true },
"custom": { "configured": true, "installed": 1, "available": 2, "update_available": true, "commands": ["catchup.md"], "scripts": ["helper.sh"] },
"new_modules": { "skills": ["name"], "mcp": ["name"], "plugins": ["id@marketplace"] },
"installed_modules": { "skills": ["name"], "mcp": ["name"], "plugins": ["id@marketplace"] },
"agent_teams": { "enabled": true }
}
Phase 2: Present + Ask (0 Bash calls)
Show status
Present a summary from the JSON:
claude-code-setup status:
- Base: v{base.installed} installed, v{base.available} available
- Custom: v{custom.installed} installed, v{custom.available} available
- Custom commands: {custom.commands} (only if non-empty)
- Custom scripts: {custom.scripts} (only if non-empty)
- Agent Teams: enabled / not configured
Modules available to install:
Skills: {new_modules.skills}
MCP Servers: {new_modules.mcp}
External Plugins: {new_modules.plugins}
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.
- 1mo ago First seen · 306 lines · 0 tokens per session scan E 92cd98729eae
claude-code-setup is a command published in the GitHub repository b33eep/claude-code-setup (57 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,235 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-30.
Other commands, from other repositories
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
ccc-orchestrate
Run a sequential multi-agent workflow (feature, bugfix, refactor, security or custom chain) with structured handoffs, plus optional tmux and worktree workers for long-running sessions. Use when a task needs planner, implementer and reviewer stages in order.
ralph-help
Explain Ralph Loop plugin and available commands.
design
A command that turns an existing plan into a detailed technical design for building the feature.