agentmods.dev

init-project

A command that prepares a new software project with a CLAUDE.md instruction file and standard documentation folders. It detects the project's tools and asks whether the instructions are private or shared with a team.

In plain words
What is it for?
Use it at project start to create CLAUDE.md, configure .gitignore, create docs/records and docs/notes, and optionally make a Git commit.
Why use it?
It gives a new project a consistent place for development instructions, records, and private notes.

Command

56 3mo ago A scan 0 tokens original MIT
View the source file b33eep/claude-code-setup
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/b33eep/claude-code-setup/init-project
Clone the repo
git clone --depth 1 https://github.com/b33eep/claude-code-setup
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 381 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.00000 $0.00381
Opus 5 $0.00000 $0.00191
Sonnet 5 $0.00000 $0.00076
Haiku 4.5 $0.00000 $0.00038

Measured 2d ago against content hash 96ad85e5c91f, 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.

commands/init-project.md · 49 lines

What it actually says

Init Project: Set Up New Project

Initialize a new project with CLAUDE.md and folder structure.

Tasks

  1. Analyze project

    • Check for existing files (package.json, pyproject.toml, Cargo.toml, etc.)
    • Detect tech stack and framework
    • Check if Git repository

  2. Ask about sharing mode

    Ask the user:

    How will you use CLAUDE.md in this project?

1) Solo - Add to .gitignore (personal workflow, not shared)
2) Team - Track in Git (shared context for all developers)
    • Solo: Add CLAUDE.md to .gitignore
    • Team: Keep CLAUDE.md tracked in Git

  3. Create CLAUDE.md

    • Read template from ~/.claude/templates/CLAUDE.template.md
    • Fill in detected project info
    • Add common development commands

  4. Create folder structure

    • Create docs/records/ if it doesn't exist
    • Create docs/notes/ if it doesn't exist

  5. Update .gitignore

    • Add docs/notes/ to .gitignore (always, for private notes)
    • If Solo mode: Also add CLAUDE.md to .gitignore
    • Create .gitignore if it doesn't exist

  6. Git commit (if Git repo)

    • Stage CLAUDE.md (if Team mode), .gitignore, and docs/records/
    • Commit: chore: add CLAUDE.md project setup

Output

  • Summary of what was created
  • Detected tech stack
  • Sharing mode (Solo/Team)
  • Suggested next steps
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 · 49 lines · 0 tokens per session scan A 96ad85e5c91f

Subscribe to this mod's changes

init-project is a command published in the GitHub repository b33eep/claude-code-setup (56 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 381 tokens. 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.

Git and workflowProductivityWriting and docsaiai-agentsanthropicclaudeclaude-codeclaude-code-plugin
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens