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.
npx skills add shandar/pwp-plugin --skill pwp-bootstrapgit clone --depth 1 https://github.com/shandar/pwp-pluginWrote 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.
[](https://agentmods.dev/skills/shandar/pwp-plugin/pwp-bootstrap)<a href="https://agentmods.dev/skills/shandar/pwp-plugin/pwp-bootstrap"><img src="https://agentmods.dev/badge/skills/shandar/pwp-plugin/pwp-bootstrap/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.
<a href="https://agentmods.dev/skills/shandar/pwp-plugin/pwp-bootstrap"><img src="https://agentmods.dev/badge/skills/shandar/pwp-plugin/pwp-bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00104 | $0.00765 |
| Opus 5.5 | $0.00042 | $0.00306 |
| Sonnet 5.5 | $0.00021 | $0.00153 |
| Haiku 4.5 | $0.00010 | $0.00076 |
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 1mo 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.
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
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.
- 1mo ago First seen · 97 lines · 104 tokens per session scan A 7bfece555b55
pwp-bootstrap is a skill published in the GitHub repository shandar/pwp-plugin (1 stars, last pushed 7mo ago), licensed MIT. It adds 104 tokens to every session and 765 once invoked, about $0.0004 per session on Opus 5.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.
Other skills, from other repositories
team-workspace
Use to set up or work with a SHARED, git-backed team workspace for artifacts a team co-owns — team charters, strategy docs, decision records — kept strictly separate from your private reflections, which never leave your machine. Trigger phrases include "share our team charter with the team", "set up a shared…
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
genshijin-commit
A guide for writing short Git commit messages in Conventional Commits format, a shared style that labels changes such as features, fixes, tests, and documentation. It supports Japanese and English and emphasizes explaining why a change was made.
catchup
Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.