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 agentmods add skills/tobzh30/claude-project-bootstrap/github-project-setupnpx skills add toBzh30/Claude-Project-Bootstrap --skill github-project-setupgit clone --depth 1 https://github.com/toBzh30/Claude-Project-BootstrapWhat 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 | $0.00142 | $0.09993 |
| Opus 5 | $0.00071 | $0.04997 |
| Sonnet 5 | $0.00028 | $0.01999 |
| Haiku 4.5 | $0.00014 | $0.00999 |
Grade A, and why
github-project-setup 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 2d 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 — 663 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/github-project-setup — Bootstrap a GitHub Project for a repo or multi-repo platform
The goal: a single project board that holds all in-flight work (features, bugs, tech-debt) with consistent custom fields so you can group, filter, and prioritise across types. The skill handles two project shapes:
- Single-repo — one Project tracks one repo. GitHub milestones for releases. Tier/Area/Priority/Effort/Mode custom fields.
- Multi-repo — one Project tracks several repos under the same org (typical for platforms with split frontend/backend/infra/runtime repos). Initiative custom field replaces Tier as the strategic axis; built-in Repository column added to default views; per-repo milestones de-emphasized in favor of cross-repo Initiatives.
Step 1 detects which case applies and the rest of the flow branches accordingly.
This skill proposes and waits for confirmation before creating issues or fields. Names are project-specific — never auto-generate without a check.
Step 0 — Working tree check
This skill writes files (issue templates, roadmap.md). Before any changes, give the user a clean baseline to git diff against if something goes wrong:
git status --short
If the output is non-empty, halt and report:
Uncommitted changes in
<N>files:<git status --short output, truncated to 10 lines if longer>This skill writes new and modified files. If anything goes wrong you'll want a clean baseline. Commit/stash first, or continue anyway?
Wait for explicit "continue" before proceeding. Don't proceed silently.
If git status --short errors (not a git repo), warn the user and ask whether to proceed without a revert baseline. Recommend git init first.
Step 1 — Preflight
Verify gh auth and scope:
gh auth status 2>&1 | grep -i scope
If project is missing from token scopes, ask the user to run:
gh auth refresh -s project
project covers both read and write. Without it, every gh project call will 403.
What ships with it
4 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.
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.
- 2d ago First seen · 663 lines · 142 tokens per session scan A 78586871b69d
github-project-setup is a skill published in the GitHub repository toBzh30/Claude-Project-Bootstrap (3 stars, last pushed 1mo ago), licensed MIT. It adds 142 tokens to every session and 9,993 once invoked, about $0.0007 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
activity
See what is happening across the team — recent sessions, handoffs, quests, and open PRs. Use for /activity, catching up after time away, or checking team-wide status at a glance.
egregore
Egregore mechanics as kernel functions — search shared memory, read team activity, create handoffs, save work, branch, and prepare notification plans without re-deriving bin/ CLI usage. Import and call directly; every function wraps the same runtime-neutral bin/ scripts the other harnesses use.
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
room-playbook
Lightweight default rules for coordinating a Room conversation without confusing chat wakeups with durable WorkGraph responsibility.
ticket-routing-playbook
How to pick the owning team and the priority for an inbound support ticket, including what to do when a ticket spans two teams. Use when triaging a ticket.
work
Pick up ready leaf yaks and implement them — dispatch subagents in isolated worktrees, then merge back to main.