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/stefan-jansen/claude-code-toolkit/setup-usergit clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkitWhat 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.00016 | $0.00393 |
| Opus 5 | $0.00008 | $0.00197 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
setup:user 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 2d 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.
What it actually says
User Configuration Setup
I'll initialize your ~/.claude/CLAUDE.md configuration file.
USER_CLAUDE_DIR="$HOME/.claude"
USER_CLAUDE_FILE="$USER_CLAUDE_DIR/CLAUDE.md"
FORCE_FLAG=false
# Check for --force flag
if [ "$1" = "--force" ]; then
FORCE_FLAG=true
fi
echo "🔧 Initializing user CLAUDE.md configuration..."
echo ""
# Create ~/.claude directory if needed
if [ ! -d "$USER_CLAUDE_DIR" ]; then
mkdir -p "$USER_CLAUDE_DIR"
echo "Created $USER_CLAUDE_DIR"
fi
# Check if file already exists
if [ -f "$USER_CLAUDE_FILE" ] && [ "$FORCE_FLAG" != true ]; then
echo "⚠️ User CLAUDE.md already exists at: $USER_CLAUDE_FILE"
echo ""
echo "Use /setup:user --force to overwrite"
exit 0
fi
# Create user CLAUDE.md
cat > "$USER_CLAUDE_FILE" << 'EOF'
# User-Level Claude Code Configuration
Personal preferences and settings that apply across all projects.
## Working Style
- Code style preferences
- Communication preferences
- Project organization preferences
## Common Tools
- Preferred development tools
- Standard aliases or shortcuts
## Personal Context
Add any personal context that helps Claude work better with you.
EOF
echo "✅ User configuration created at: $USER_CLAUDE_FILE"
echo ""
echo "Next: Edit $USER_CLAUDE_FILE to customize your preferences"
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.
- 2d ago First seen · 61 lines · 16 tokens per session scan A b47aa85435c3
setup:user is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (85 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 393 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.
Other commands, from other repositories
remember
Save something to agent memory - picks project or user scope automatically from context.
disambiguate-plan
Thorough collaborative planning with iterative disambiguation - resolves all ambiguity before planning.
pr-review
Review a GitHub pull request: analyzes changed files to select relevant reviewers, loads project and user memory, runs reviewers in parallel, lets the user pick which findings to post, then submits the review on behalf of the user via gh CLI.
dataviz
Define chart types, color encoding, and data display conventions.
ship
Pre-launch gate — six-domain checklist before any production deployment.
build
Implement the next ready task from .forge/tasks.yaml using TDD discipline.