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 toBzh30/Claude-Project-Bootstrap --skill to-prdgit clone --depth 1 https://github.com/toBzh30/Claude-Project-BootstrapWrote 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/tobzh30/claude-project-bootstrap/to-prd)<a href="https://agentmods.dev/skills/tobzh30/claude-project-bootstrap/to-prd"><img src="https://agentmods.dev/badge/skills/tobzh30/claude-project-bootstrap/to-prd/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/tobzh30/claude-project-bootstrap/to-prd"><img src="https://agentmods.dev/badge/skills/tobzh30/claude-project-bootstrap/to-prd.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.00059 | $0.00883 |
| Opus 5 | $0.00030 | $0.00441 |
| Sonnet 5 | $0.00012 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
to-prd 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 10d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill takes the current conversation context and codebase understanding and produces a PRD for an initiative-scale effort. Do NOT interview the user — just synthesize what you already know.
Scope (read first). A PRD is not a new kind of artifact — it is just a regular issue whose body is a PRD spec, at initiative scale, that holds sub-issues. It sits above the slices only in the sub-issue sense (parent ▸ children), nothing more. For discrete intent (a single feature/bug/refactor), file an issue directly per
working-agreements.md, or useto-issues; do not write a PRD — reaching for one on small work creates a second, competing intake path.
The issue/Project contract is set up by github-project-setup and recorded in .claude/gh-project.json.
Process
-
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain vocabulary from
CLAUDE.md/.claude/rules/glossary.mdthroughout the PRD, and respect.claude/rules/decisions.mdfor the area you're touching. -
Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.
A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
- Write the PRD using the template below, then publish it as an issue whose body is the PRD (per the
working-agreements.mdfiling lifecycle). SetArea/Priority; setMode=HITL— a PRD is an initiative spec, reviewed before its slices run. Its slices (created later viato-issues) become sub-issues of this issue and carry their own per-sliceMode.
Problem Statement
The problem that the user is facing, from the user's perspective.
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.
- 10d ago First seen · 79 lines · 59 tokens per session scan A 4194d00ddb9a
to-prd is a skill published in the GitHub repository toBzh30/Claude-Project-Bootstrap (3 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 883 once invoked, about $0.0003 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.
Other skills, from other repositories
project-standard-spec
Spec maintainer for Big Emotion Project Standard. Reads Confluence (Requirements / Decisions / Architecture) as the source of truth, helps you investigate a problem, structures the reflection, and produces drafts — Pending REQ/DEC/ARCH sections on Confluence + matching Jira tickets in the Jira project configured in…
issue-train
Batch-process every open GitHub issue in a list — triage, detect existing PR linkage, detect silent fixes in already-merged PRs, close issues that are no longer pertinent, then plan + build + open one PR per remaining actionable issue with Closes.
project-standard-bootstrap-confluence
One-shot bootstrap of the Confluence spec tree (Requirements / Decisions / Architecture / Obsolete) for Big Emotion Project Standard. Creates the four skeleton subpages under the project's engineering root page, records their IDs in the spec config, writes the sentinel, then refuses second runs. Use only when…
project-standard-ticket
End-to-end local automation for a single Jira ticket on the Big Emotion Project Standard repo. Paste a Jira ticket URL (or key) and the skill self-assigns the ticket, reads it, refines it, creates the Jira sub-tasks, branches off the integration branch in an isolated git worktree, implements the work in parallel via…
merge-train
Batch-process a list of open GitHub pull requests. From a GitHub PRs URL (or the current repo), enumerate every open PR, compute the safe merge order from dependencies, then per PR fix CI, resolve merge conflicts, run a code review, and assign a status (mergeable / changes-required / blocked-by-order). Presents one…
{{project_slug}}-bootstrap-confluence
One-shot bootstrap of the Confluence spec tree (Requirements / Decisions / Architecture / Obsolete) for {{projectdisplayname}}. Creates the four skeleton subpages under the project's engineering root page, records their IDs in the spec config, writes the sentinel, then refuses second runs. Use only when initializing…