setup-toolkit

A project setup command for configuring Claude Code in a new repository. It detects the project type, asks which development features and tool connections to enable, and creates configuration folders.

In plain words
What is it for?
Use it to identify a project as web, Python, trading, or general development, choose tools and permissions, and create the initial .claude structure.
Why use it?
It gives a new project a guided starting configuration instead of requiring every setting to be created by hand.

Command

Install

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.

agentmods
npx agentmods add commands/stefan-jansen/claude-code-toolkit/setup-toolkit
Clone the repo
git clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkit
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,762 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.01762
Opus 5 $0.00004 $0.00881
Sonnet 5 $0.00002 $0.00352
Haiku 4.5 $0.00001 $0.00176

Measured yesterday against content hash a1fdb68b0a86, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

setup-toolkit scanned grade D with 2 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 yesterday.

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/hooks/init-transition.sh << 'HOOK_EOF'

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"Bash(rm -rf:*)",
commands/setup-toolkit.md · 272 lines

How it starts

The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are helping set up Claude Code configuration for a project.

Project Setup Workflow

Step 1: Detect Project Context

First, examine the current directory to understand the project type:

pwd
ls -la

Look for indicators:

  • Web project: package.json, Django files (manage.py, settings.py), templates/
  • Python project: pyproject.toml, setup.py, requirements.txt
  • Quant/Trading: mentions of trading, strategies, backtesting
  • General: anything else

Step 2: Ask User for Configuration

Use AskUserQuestion to determine:

  1. Project type (affects which plugins to enable):

    • General development (system, workflow, memory, development)
    • Web development (+ web-development)
    • Quantitative/Trading (+ quant)
    • Multiple types (let them select multiple)
  2. MCP servers (which ones to enable):

    • Chrome DevTools (browser automation, web testing)
    • Serena (semantic code understanding)
    • Context7 (documentation access)
    • All standard servers
  3. Permissions (optional):

    • Standard (allow common operations)
    • Strict (ask for most operations)
    • Custom (ask user to specify later)

Step 3: Create Directory Structure

mkdir -p .claude/hooks
mkdir -p .claude/transitions

Step 4: Create Transition Hook

Create .claude/hooks/init-transition.sh:

cat > .claude/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/hooks/init-transition.sh

Read the full file on GitHub · 272 lines

Changes

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.

  1. yesterday First seen · 272 lines · 8 tokens per session scan D a1fdb68b0a86

Subscribe to this mod's changes

setup-toolkit is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (85 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 1,762 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.