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-existinggit 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.00012 | $0.01298 |
| Opus 5 | $0.00006 | $0.00649 |
| Sonnet 5 | $0.00002 | $0.00260 |
| Haiku 4.5 | $0.00001 | $0.00130 |
Grade B, and why
setup:existing scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat >> .claude/transitions/$(date +%Y-%m-%d)/$(date +%H).md << 'EOF' How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Claude Framework to Existing Project
I'll add the Claude Code Framework to your existing project, auto-detecting the language and framework.
readonly CLAUDE_DIR=".claude"
echo "🔧 Adding Claude Code Framework to existing project..."
echo ""
# Auto-detect project type using shared-setup-patterns skill
echo "Detecting project characteristics..."
# Use framework detection patterns from skill to identify:
# - Language (Python, JavaScript, Go, Rust)
# - Framework (FastAPI, Django, Next.js, Express, etc.)
# - Tools (pytest, Jest, etc.)
# Create .claude directory structure
mkdir -p $CLAUDE_DIR/work
mkdir -p $CLAUDE_DIR/memory
mkdir -p $CLAUDE_DIR/reference
mkdir -p $CLAUDE_DIR/hooks
mkdir -p $CLAUDE_DIR/transitions
# Create hourly transition hook
cat > $CLAUDE_DIR/hooks/init-transition.sh << 'HOOK_EOF'
#!/bin/bash
# Initialize hourly transition file for session progress tracking
set -e
PROJECT_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
TRANSITIONS_DIR="$PROJECT_ROOT/.claude/transitions"
TODAY=$(date +%Y-%m-%d)
HOUR=$(date +%H)
TODAY_DIR="$TRANSITIONS_DIR/$TODAY"
HOURLY_FILE="$TODAY_DIR/${HOUR}.md"
mkdir -p "$TODAY_DIR"
if [ ! -f "$HOURLY_FILE" ]; then
echo "# Session Progress: $TODAY ${HOUR}:00" > "$HOURLY_FILE"
echo "" >> "$HOURLY_FILE"
echo "---" >> "$HOURLY_FILE"
echo "" >> "$HOURLY_FILE"
fi
exit 0
HOOK_EOF
chmod +x $CLAUDE_DIR/hooks/init-transition.sh
echo "✅ Created .claude/hooks/init-transition.sh (hourly progress tracking)"
# Get absolute path for hook
HOOK_PATH="$(pwd)/$CLAUDE_DIR/hooks/init-transition.sh"
# Create settings.json with plugins and hooks
cat > $CLAUDE_DIR/settings.json << SETTINGS_EOF
{
"extraKnownMarketplaces": {
"local": {
"source": {
"source": "directory",
"path": "/home/stefan/agents/plugins"
}
}
},
"enabledPlugins": {
"system@local": true,
"workflow@local": true,
"memory@local": true,
"development@local": true,
"transition@local": true
},
"hooks": {
"UserPromptSubmit": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "$HOOK_PATH"
}
]
}
]
}
}
SETTINGS_EOF
echo "✅ Created .claude/settings.json with plugins + transition hook"
echo ""
echo "I'll also create:"
echo " - .claude/memory/* (project knowledge files)"
echo " - CLAUDE.md (project instructions)"
echo ""
# Create project CLAUDE.md with progress tracking
PROJECT_NAME=$(basename "$PWD")
cat > CLAUDE.md << 'CLAUDE_EOF'
# PROJECT_NAME_PLACEHOLDER
## 🔄 Session Progress Tracking (MANDATORY)
**Write progress to the current hourly transition file throughout the session.**
**File**: `.claude/transitions/YYYY-MM-DD/HH.md` (hook creates this automatically)
### When to Update (Every 15-20 minutes or at milestones)
Append to the **current hour's file** with:
```markdown
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 · 178 lines · 12 tokens per session scan B 9ed5c9d09b1e
setup:existing is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (85 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,298 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
build
Implement the next ready task from .forge/tasks.yaml using TDD discipline.
db
Design schema, migrations, indexes, and query patterns with safety guardrails.