init-project

A setup command that creates a Claude Code project structure, including guidance files, documentation, hooks, skills, agents, and MCP configuration. It checks the existing project and adapts to its language, framework, and folders.

In plain words
What is it for?
Use it when starting a new project or adding Claude Code structure to an existing one.
Why use it?
It removes the need to assemble the project setup by hand and avoids creating folders that do not fit an existing codebase.

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/whchoi98/project-init/init-project
Clone the repo
git clone --depth 1 https://github.com/whchoi98/project-init
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,067 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00035 $0.05067
Opus 5 $0.00017 $0.02534
Sonnet 5 $0.00007 $0.01013
Haiku 4.5 $0.00003 $0.00507

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

Security

Grade A, and why

init-project 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.

plugins/project-init/commands/init-project.md · 443 lines

How it starts

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

Initialize Claude Code Project Structure

Set up a complete Claude Code project structure in the target directory. Adapts to existing projects by detecting language, framework, and directory layout.

Step 1: Determine Target Directory

Target: $ARGUMENTS

  • If a path is provided, use it as the project root
  • If empty, use the current working directory
  • If the directory doesn't exist, create it
ls -la <target_dir> 2>/dev/null

Step 2: Detect Existing Project

Scan for existing project files to determine if this is a new or existing project:

# Detect language/framework
ls package.json pyproject.toml go.mod Cargo.toml pom.xml build.gradle Gemfile composer.json 2>/dev/null

# Detect existing source directories
ls -d src/ app/ lib/ cmd/ pkg/ internal/ components/ pages/ routes/ 2>/dev/null

# Check dependency files for framework detection
cat package.json 2>/dev/null | head -30
cat pyproject.toml 2>/dev/null | head -30

If existing project detected:

  • Do NOT create src/api/ or src/persistence/ if they don't match the project
  • Instead, identify the actual source directories and create module CLAUDE.md files for each
  • Adapt Tech Stack, Commands, and Conventions based on detected framework
  • Warn the user before overwriting any existing files

Project type detection rules:

File Found Project Type Source Dirs Key Commands
package.json Node.js src/, app/, lib/, components/ npm/yarn/pnpm
pyproject.toml / requirements.txt Python src/, app/, lib/ pip, pytest, ruff
go.mod Go cmd/, pkg/, internal/ go build, go test
Cargo.toml Rust src/ cargo build, cargo test
pom.xml / build.gradle Java/Kotlin src/main/, src/test/ mvn, gradle
None detected New project src/api/, src/persistence/ (ask user)

If new project (no existing files):

  • Ask the user for project name, description, tech stack
  • Create the default src/api/ and src/persistence/ structure

Read the full file on GitHub · 443 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. 2d ago First seen · 443 lines · 35 tokens per session scan A ee4adb3d395e

Subscribe to this mod's changes

init-project is a command published in the GitHub repository whchoi98/project-init (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 5,067 once invoked, about $0.0002 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-31.