An interactive command for configuring a project’s environment variables and settings, including GitHub, Docker, analytics, and other services. It creates or updates the `.env` file while preserving `.env.example` as a template.

Use it when starting or resetting a project setup, creating environment files, checking WSL or Windows environments, and configuring connected services.

It reduces setup mistakes by checking existing files, protecting secrets from version control, and walking through the required configuration.

How TheDecipherist/claude-code-mastery-project-starter-kit configures

Reuse

Borrowing it

Nothing to install: this file belongs to TheDecipherist/claude-code-mastery-project-starter-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/TheDecipherist/claude-code-mastery-project-starter-kit/main/.claude/commands/setup.md

Clone the repo

git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/setup/github.svg)](https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/setup)

Your own site

<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/setup"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/setup"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,211 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.03211
Opus 5.5	$0.00007	$0.01284
Sonnet 5.5	$0.00003	$0.00642
Haiku 4.5	$0.00002	$0.00321

Measured 2mo ago against content hash 3e9811a09cdc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

.claude/commands/setup.md · 338 lines

How it starts

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

Project Setup

Walk the user through configuring all environment variables and project settings. Creates or updates the .env file with real values while keeping .env.example as the template.

Arguments: $ARGUMENTS

If --reset is passed, start fresh (re-ask all questions even if .env already has values).

Step 0 — Check Current State

# Does .env exist?
ls .env 2>/dev/null

# Does .env.example exist?
ls .env.example 2>/dev/null

# Is .env in .gitignore?
grep -q "^\.env$" .gitignore 2>/dev/null && echo ".env is gitignored" || echo "WARNING: .env NOT in .gitignore"

If .env doesn't exist, create it from .env.example. If .env.example doesn't exist, create a blank .env. If .env is NOT in .gitignore, add it immediately before proceeding.

Step 0.5 — Development Environment Check (WSL)

Detect the current environment:

# Check if running on WSL
uname -r 2>/dev/null | grep -qi "microsoft\|wsl" && echo "WSL_DETECTED=true" || echo "WSL_DETECTED=false"

# Check if running on Windows (not WSL)
uname -s 2>/dev/null | grep -qi "mingw\|msys\|cygwin" && echo "WINDOWS_NATIVE=true" || echo "WINDOWS_NATIVE=false"

# Check current working directory — is the project on the Windows filesystem from WSL?
pwd | grep -q "^/mnt/c\|^/mnt/d" && echo "PROJECT_ON_WINDOWS_FS=true" || echo "PROJECT_ON_WINDOWS_FS=false"

If on Windows (native, not WSL):

Tell the user:

⚠️  You're running on Windows natively.

STRONGLY RECOMMENDED: Use WSL 2 (Windows Subsystem for Linux) instead.

Why this matters:
  • HMR (hot module replacement) is 5-10x faster in WSL
  • Playwright tests run significantly faster on native Linux
  • File watching (nodemon, tsx watch, next dev) is dramatically more reliable
  • Node.js filesystem operations avoid the NTFS translation layer
  • Claude Code itself runs faster with native Linux tools (grep, find, git)

Setup (one time):
  1. Open PowerShell as admin: wsl --install
  2. Restart your computer
  3. Install VS Code extension: "WSL" (ms-vscode-remote.remote-wsl)
  4. Open VS Code → click green "><" bottom-left → "Connect to WSL"
  5. Clone your projects INSIDE WSL: ~/projects/ (NOT /mnt/c/)

After setup, VS Code runs its backend inside WSL while the UI stays on Windows.
Everything just works — terminal, extensions, git, Node.js — all running natively in Linux.

Read the full file on GitHub · 338 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.

2mo ago First seen · 338 lines · 17 tokens per session scan A 3e9811a09cdc

Subscribe to this mod's changes

setup is a command published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (342 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 3,211 once invoked, about $0.0001 per session on Opus 5.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.

DevOps and cloud Productivity

setup next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
setupTheDecipherist/claude-code-mastery-project-starter-kit	Command	342	4mo ago	MIT	A	17	Claude Code
wsdanielmiessler/LifeOS	Command	20k	yesterday	MIT	A	0	Claude Code
cancel-ralphanthropics/claude-plugins-official	Command	46k	yesterday	Apache-2.0	A	4	Claude Code
engage.actionshypnguyen1209/offensive-claude	Command	412	15d ago	MIT	A	11	Claude Code
focusData-Wise/claude-plugins	Command	7	yesterday	MIT	A	0	Claude Code
stuckData-Wise/claude-plugins	Command	7	yesterday	MIT	A	0	Claude Code
quickstartorq-ai/assistant-plugins	Command	6	2d ago	MIT	A	23	Claude Code

claude-code-mastery-project-starter-kit: Command for Claude Code