project-setup

A project-starting command that creates a standard folder layout, setup files, development settings, and version-control configuration.

In plain words
What is it for?
Use it to create a README, .gitignore, environment template, source and test folders, documentation folders, and language-specific project structure.
Why use it?
It removes the repetitive decisions and manual setup involved in starting a new software project.

Command for Claude Code

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/justdvp/claude-code-templates/project-setup
Clone the repo
git clone --depth 1 https://github.com/Justdvp/claude-code-templates

Made for: Claude Code.

Per session 0 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,702 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00000 $0.01702
Opus 5 $0.00000 $0.00851
Sonnet 5 $0.00000 $0.00340
Haiku 4.5 $0.00000 $0.00170

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

Security

Grade C, and why

project-setup scanned grade C 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.

Recursive force deletehighDestructive command

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

"clean": "rm -rf dist/"
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

cli-tool/templates/common/.claude/commands/project-setup.md · 316 lines

How it starts

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

Project Setup Helper

Set up new projects with proper structure and best practices.

Purpose

This command helps you set up new projects with proper directory structure, configuration files, and development environment.

Usage

/project-setup

What this command does

  1. Creates project structure with standard directories
  2. Sets up configuration files (.gitignore, README, etc.)
  3. Initializes version control and development tools
  4. Configures environment files and dependencies
  5. Follows language-specific conventions and best practices

Project Structure Templates

Generic Project Structure

project-name/
├── README.md                 # Project documentation
├── .gitignore               # Git ignore rules
├── .env.example             # Environment variables template
├── LICENSE                  # Project license
├── CHANGELOG.md             # Version history
├── docs/                    # Documentation
│   ├── API.md
│   ├── CONTRIBUTING.md
│   └── DEPLOYMENT.md
├── src/                     # Source code
│   ├── main/
│   ├── utils/
│   └── config/
├── tests/                   # Test files
│   ├── unit/
│   ├── integration/
│   └── fixtures/
├── scripts/                 # Build and deployment scripts
│   ├── build.sh
│   ├── deploy.sh
│   └── setup.sh
└── config/                  # Configuration files
    ├── development.yml
    ├── production.yml
    └── testing.yml

Web Application Structure

web-app/
├── public/                  # Static assets
│   ├── index.html
│   ├── favicon.ico
│   └── assets/
│       ├── css/
│       ├── js/
│       └── images/
├── src/                     # Source code
│   ├── components/          # Reusable components
│   ├── pages/              # Page components
│   ├── services/           # API services
│   ├── utils/              # Utility functions
│   ├── styles/             # Stylesheets
│   └── config/             # Configuration
├── tests/                   # Test files
└── build/                   # Build output

Read the full file on GitHub · 316 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 · 316 lines · 0 tokens per session scan C be0f448848b0

Subscribe to this mod's changes

project-setup is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,702 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.