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-issuesgit 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-issues)<a href="https://agentmods.dev/skills/tobzh30/claude-project-bootstrap/to-issues"><img src="https://agentmods.dev/badge/skills/tobzh30/claude-project-bootstrap/to-issues.svg" alt="Measured on agentmods" 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.00053 | $0.01192 |
| Opus 5 | $0.00026 | $0.00596 |
| Sonnet 5 | $0.00011 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
to-issues 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 8d 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.
To Issues
Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
This marketplace's issue/Project contract is set up by github-project-setup and recorded in .claude/gh-project.json; the filing lifecycle (labels, fields, report-back) lives in the repo's working-agreements.md. Follow that contract when publishing — don't fall back to bare gh issue create.
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes an issue reference (number, URL, or path) as an argument, fetch it from GitHub and read its full body and comments.
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain vocabulary from CLAUDE.md / .claude/rules/glossary.md, and respect .claude/rules/decisions.md for the area you're touching.
3. Draft vertical slices
Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer. (When a slice spans repos, see the tdd skill's "Cross-repo slices" — the slice splits at the contract, with one real cross-repo e2e proof.)
Each slice gets an execution Mode matching the Mode Project field:
HITL(default) — needs human interaction at a checkpoint: an architectural decision, a design review.AFK— clears the eligibility bar inworking-agreements.md→ "AFK vs HITL issues": unambiguous scope, no unresolved architectural fork, no irreversible/outward-facing step, a plausible test seam, bounded.AFKis earned, not preferred-by-default — when unsure, leave itHITL.
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.
- 8d ago First seen · 97 lines · 53 tokens per session scan A 81b2af028570
to-issues is a skill published in the GitHub repository toBzh30/Claude-Project-Bootstrap (3 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,192 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…