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/vindm/dotclaude/bootstrapnpx skills add vindm/dotclaude --skill bootstrapgit clone --depth 1 https://github.com/vindm/dotclaudeWhat 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.00084 | $0.02708 |
| Opus 5 | $0.00042 | $0.01354 |
| Sonnet 5 | $0.00017 | $0.00542 |
| Haiku 4.5 | $0.00008 | $0.00271 |
Grade A, and why
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 yesterday.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dotclaude:bootstrap — thin generator over the consumable base
The base is consumed, not authored. Enabling the dotclaude plugin already gives the project the universal layer: the operating-discipline skill (how to work), the auditor agents (code-review, pre-flight, test-architect, skill-vs-code-audit, product-direction-validator, dispatchable as dotclaude:<name>), the process/knowledge skills (knowledge-layers, decomposition), and the universal guard hooks (git-safety, secret-leak, file-size, session-start git context, uncommitted-on-clear). The companion dotclaude-design plugin adds the design/UX auditors (a11y-audit, ux-audit, interaction-audit, flow-audit, pages-audit, design-token-audit, product-designer) and design-focused skills for projects with a human-facing surface. Bootstrap does NOT re-author any of these.
Bootstrap authors only what a shared file cannot carry — the project-specific layer:
| Authored by bootstrap (un-shareable) | Consumed from the plugin (do NOT author) |
|---|---|
| Identity — vision / ICP / moat / stage (CLAUDE.md opening) | Process discipline (operating-discipline skill) |
Architecture — layers / boundaries + project boundary hooks + dotclaude.yml config for the config-needing guard templates |
The universal guard hooks (hooks/hooks.json) |
Quality bar — a non-design quality bar where one applies (e.g. api-north-star.md) |
Design's north-star + design-system reference — authored by the companion dotclaude-design plugin's /dotclaude:design, not by bootstrap |
Knowledge graph — docs/ structure + the project's task-classification routing table + capability map |
The domain skills |
A THIN local CLAUDE.md — identity + architecture + task table + DoD (project verification commands) + a pointer to the consumed methodology |
— |
The thin local CLAUDE.md is the headline change from older bootstrap: it carries identity + project routing + project verification, and points at the consumed operating-discipline skill for the universal "how you work" rather than restating ~250 lines of it.
What ships with it
1 file 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.
- yesterday First seen · 100 lines · 0 tokens per session scan A bfebfc5626d0
bootstrap is a skill published in the GitHub repository vindm/dotclaude (1 stars, last pushed 5d ago), licensed MIT. It adds 84 tokens to every session and 2,708 once invoked, about $0.0004 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
claude-md-review
Audit a CLAUDE.md file for the patterns that actually degrade Claude Code's output — vagueness, unnamed files, stale facts, and bloat. Use when asked to review, audit, improve, shrink, or fix a CLAUDE.md, and when a project's results feel inconsistent or Claude keeps rediscovering the same context.
git-commit-helper
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
code-reviewer
Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, git diff, code edits, quality mentions.
test-generator
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.
api-documenter
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.
readme-updater
Keep README files current with project changes. Use when project structure changes, features added, or setup instructions modified. Suggests README updates based on code changes. Triggers on significant project changes, new features, dependency changes.