project-init

project-init is a skill for Claude Code from bodangren/git-workflow. It costs 47 tokens per session (1,510 once invoked), scanned C, original, MIT.

A project setup workflow that creates the folders and configuration needed for spec-driven development, where written requirements guide implementation. It sets up locations for permanent specifications and proposed changes.

In plain words
What is it for?
Use it when starting a project or adding AgenticDev to an existing project without documentation; projects that already have docs/ should use the migration workflow instead.
Why use it?
It gives a new project a predictable place for requirements and change proposals from the beginning.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash skills/agent-integrator/scripts/update-agents-file.sh.

Good fit Use it when starting a project or adding AgenticDev to an existing project without documentation; projects that already have docs/ should use the migration workflow instead.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/bodangren/git-workflow
agentmods
npx agentmods add skills/bodangren/git-workflow/project-init

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.

agentmods badge for project-init

README.md
[![agentmods](https://agentmods.dev/badge/skills/bodangren/git-workflow/project-init/github.svg)](https://agentmods.dev/skills/bodangren/git-workflow/project-init)
Your own site
<a href="https://agentmods.dev/skills/bodangren/git-workflow/project-init"><img src="https://agentmods.dev/badge/skills/bodangren/git-workflow/project-init/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.

agentmods 80×15 button for project-init

Your own site · 80×15
<a href="https://agentmods.dev/skills/bodangren/git-workflow/project-init"><img src="https://agentmods.dev/badge/skills/bodangren/git-workflow/project-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,510 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01510
Opus 5.5 $0.00019 $0.00604
Sonnet 5.5 $0.00009 $0.00302
Haiku 4.5 $0.00005 $0.00151

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

Security

Grade C, and why

project-init 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/init-project.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

- Remove incorrect directories: `rm -rf docs/`
.claude/skills/project-init/SKILL.md · 217 lines

How it starts

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

Project Init Skill

Purpose

Initialize a new project with the AgenticDev directory structure and configuration files. This skill sets up the foundational folders needed for the spec-driven development workflow, creating a standard structure for specifications, change proposals, and documentation.

When to Use

Use this skill in the following situations:

  • Starting a completely new project that will use AgenticDev
  • Adding AgenticDev methodology to an existing project with no existing documentation
  • Setting up a consistent structure for spec-driven development
  • Ensuring project follows AgenticDev conventions from the beginning

Important: If the project already has documentation in a docs/ directory, use the project-migrate skill instead. It will properly catalog, categorize, and migrate existing documentation into the AgenticDev structure while preserving git history and updating links.

Prerequisites

  • Write permissions to the target directory
  • Git repository already initialized (recommended but not required)

Workflow

Step 1: Assess the Current Project State

Before initializing, determine:

  • Is this a brand new project or an existing codebase?
  • Does a docs/ directory already exist?
  • If docs/ exists, does it contain markdown files?
  • Where should the AgenticDev structure be created?

Decision Tree:

  • No docs/ directory: Proceed with project-init (this skill)
  • Empty docs/ directory: Proceed with project-init (this skill)
  • docs/ with existing markdown files: Use project-migrate skill instead

The init-project.sh script will automatically detect existing documentation and suggest using project-migrate if appropriate.

Step 2: Run the Initialization Script

Execute the helper script to create the directory structure:

For current directory:

bash scripts/init-project.sh

For a specific directory:

bash scripts/init-project.sh -d /path/to/project

The script will create:

  • docs/specs/ - Source-of-truth for approved specifications
  • docs/changes/ - Staging area for proposed changes (Spec PRs)

Read the full file on GitHub · 217 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 217 lines · 47 tokens per session scan C 354ab7520e0c

Subscribe to this mod's changes

project-init is a skill published in the GitHub repository bodangren/git-workflow (11 stars, last pushed 10mo ago), licensed MIT. It adds 47 tokens to every session and 1,510 once invoked, about $0.0002 per session on Opus 5.5. 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-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens