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 shawnclybor/clybor-claude-tooling --skill project-bootstrapgit clone --depth 1 https://github.com/shawnclybor/clybor-claude-toolingWrote 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/shawnclybor/clybor-claude-tooling/project-bootstrap)<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/project-bootstrap"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/project-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/shawnclybor/clybor-claude-tooling/project-bootstrap"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/project-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.00160 | $0.01591 |
| Opus 5.5 | $0.00064 | $0.00636 |
| Sonnet 5.5 | $0.00032 | $0.00318 |
| Haiku 4.5 | $0.00016 | $0.00159 |
Grade A, and why
project-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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Bootstrap
Sets up a new project with tooling from the catalog. Seven steps, one at a time.
The catalog lives at the clybor-claude-tooling repo root: catalog.json indexes every
asset under assets/skills/<id>/ with its domains, requirements, and adaptation tokens.
This skill is the consumer side: filter, propose, install, personalize, record.
Step 1 — Read the catalog, profile the project
Locate the catalog repo (default ~/gits/clybor-claude-tooling/; ask if not found).
Read catalog.json. Then ask the user AT MOST 4 questions, in one round:
- Project type — consulting engagement / coding project / research / mixed?
- Client surface — Claude Code, Cowork, or both? (filters on each asset's
targets) - Domains in play — pick from the domain values present in the catalog (show them).
- Seed values — the project/client name and any obvious adaptation values (e.g., where notes and tasks should live, if known).
If the user's request already answers a question, don't re-ask it. Fewer than 4 is better than 4.
Step 2 — Propose the install set
Filter the catalog on targets + domains. Present the proposed set as a short list,
one line per asset: name, one-line rationale drawn from its summary, and its
adaptation tokens. Mark anything borderline as optional. Wait for approval or edits.
Step 3 — Copy assets in
For each approved asset, copy assets/skills/<id>/ into the project's
.claude/skills/<id>/. Copy semantics (never destructive):
- If the destination file does not exist → copy.
- If it exists → write the new version alongside as
<file>.newand tell the user to diff before merging. Never overwrite.
Step 4 — Route every installed asset in CLAUDE.md
An installed skill the router never mentions is unreachable. A cold session follows
CLAUDE.md's routing table and nothing else — it will not discover a skill by listing
.claude/skills/. Installing without routing ships a capability that cannot fire.
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 · 128 lines · 160 tokens per session scan A c3fc3d9aaa72
project-bootstrap is a skill published in the GitHub repository shawnclybor/clybor-claude-tooling (6 stars, last pushed 5d ago), licensed MIT. It adds 160 tokens to every session and 1,591 once invoked, about $0.0006 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
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
quick
Execute an ad-hoc task with atomic commits. Skips full plan/review.
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
debug
Systematic debugging with hypothesis testing. Persistent across sessions.
explore
Explore ideas, think through approaches, and route insights to the right artifacts.
resume
Pick up where you left off. Restores context and suggests next action.