pwp-bootstrap

A process for setting up a new software project from an empty folder, including its repository, configuration, structure, and first commit.

In plain words
What is it for?
Use it when starting a codebase, initializing version control, adding standard project files, configuring TypeScript and code-quality tools, and creating an initial project structure.
Why use it?
It prevents basic setup decisions and development tools from being missed or applied inconsistently later.

Skill for Claude CodeCodex

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 skills/shandar/pwp-plugin/pwp-bootstrap
Any agent
npx skills add shandar/pwp-plugin --skill pwp-bootstrap
Clone the repo
git clone --depth 1 https://github.com/shandar/pwp-plugin

Made for: Claude Code, Codex.

Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 765 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.00104 $0.00765
Opus 5 $0.00052 $0.00382
Sonnet 5 $0.00021 $0.00153
Haiku 4.5 $0.00010 $0.00076

Measured yesterday against content hash 7bfece555b55, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pwp-bootstrap 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 yesterday.

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.

skills/pwp-bootstrap/SKILL.md · 97 lines

How it starts

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

Project Bootstrap Skill

This skill defines how to start a new project from scratch. Covers repository setup, folder structure, configuration, and the first commit.

Bootstrap Mindset

  • Foundation before features. A well-initialized project saves hundreds of hours later.
  • Conventions from day one. It's 10x harder to adopt conventions after code exists.
  • Ship the skeleton first. Get the project building and deploying before writing features.
  • Document decisions early. The first ADR is the cheapest to write.

Bootstrap Checklist

Phase 1: Repository Foundation (5 min)

  • Git initialized
  • Package manager configured
  • .gitignore created
  • First commit: chore: initialize repository

Phase 2: Governance Files (5 min)

  • README.md — name, description, quick start
  • LICENSE
  • .env.example with placeholder values

Phase 3: Tooling Configuration (10 min)

  • TypeScript (strict mode)
  • Linter (ESLint / Biome)
  • Formatter (Prettier or equivalent)
  • Build tool (Vite, Next.js, etc.)

Phase 4: Project Structure (5 min)

{project}/
├── src/
│   ├── components/
│   ├── lib/
│   ├── types/
│   ├── hooks/
│   ├── api/
│   └── styles/
├── public/
├── docs/plans/
├── tests/
├── .env.example
├── .gitignore
├── README.md
├── tsconfig.json
└── package.json

Phase 5: Hello World (5 min)

  • Entry point created
  • Builds successfully
  • Runs locally
  • TypeScript compiles cleanly

Phase 6: CI/CD Setup (optional, 10 min)

  • GitHub Actions for build + type check
  • Deploy pipeline configured
  • Branch protection on main

CLAUDE.md Template

# Project: {name}

## Stack
- {Framework}: {version}
- {Language}: {version}

## Conventions
- Components: PascalCase, co-located with styles/tests
- Utilities: camelCase, in src/lib/
- Tests: co-located as {file}.test.ts

## Commands
- `npm run dev` — development server
- `npm run build` — production build
- `npm test` — run tests
- `npx tsc --noEmit` — type check

Read the full file on GitHub · 97 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. yesterday First seen · 97 lines · 104 tokens per session scan A 7bfece555b55

Subscribe to this mod's changes

pwp-bootstrap is a skill published in the GitHub repository shandar/pwp-plugin (1 stars, last pushed 6mo ago), licensed MIT. It adds 104 tokens to every session and 765 once invoked, about $0.0005 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.