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 jkm-4314/claude-code-skills --skill bootstrap-projectgit clone --depth 1 https://github.com/jkm-4314/claude-code-skillsWrote 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/jkm-4314/claude-code-skills/bootstrap-project)<a href="https://agentmods.dev/skills/jkm-4314/claude-code-skills/bootstrap-project"><img src="https://agentmods.dev/badge/skills/jkm-4314/claude-code-skills/bootstrap-project/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/jkm-4314/claude-code-skills/bootstrap-project"><img src="https://agentmods.dev/badge/skills/jkm-4314/claude-code-skills/bootstrap-project.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.00054 | $0.03912 |
| Opus 5.5 | $0.00022 | $0.01565 |
| Sonnet 5.5 | $0.00011 | $0.00782 |
| Haiku 4.5 | $0.00005 | $0.00391 |
Grade A, and why
bootstrap-project 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap Project
You are setting up a new project with an opinionated standard workflow. This creates the full project infrastructure: session memory files, commit hooks, copyright headers, ROADMAP, and CLAUDE.md.
Step 1: Pre-Flight Checks
- Verify this is a git repository (
git rev-parse --git-dir). If not, ask the user if you should rungit init. - Check which of the expected files already exist:
.claude/SESSION_LOG.md.claude/CONTEXT.mdCLAUDE.mdROADMAP.md.githooks/commit-msg
- If any exist, warn the user and ask before overwriting.
Step 2: Gather Project Info
Ask the user these questions. If they say "just use defaults" or similar, infer from the repo (package.json, pyproject.toml, docker-compose.yml, etc.) and confirm before writing.
-
Project name — e.g., "Acme Widget Manager"
-
Short identifier — e.g.,
widget-mgr -
One-line description — what the project is
-
Tech stack — e.g., "FastAPI + React + PostgreSQL + Docker"
-
Project ownership — ask the user to pick one of their configured ownership profiles, or to define a new one inline. An ownership profile is a
(label, copyright-text | none)pair. Examples:Personal→ single-line copyright with the user's legal nameCompany→ multi-line copyright with the company name and a confidentiality noticeClient / Government / Open-source→ no copyright header (use this for work-for-hire, public-domain, or permissively-licensed projects)
If the user has not previously declared their profiles, ask now: "What ownership profiles should I support? For each, give me a label and the copyright text — or
nonefor no header." Save the answers for future invocations (e.g., write them to~/.claude/bootstrap-project.config.mdor note them in the global CLAUDE.md). -
Dev environment startup (optional) — commands to start backend/frontend, ports used
Step 3: Create .claude/ Memory Files
Create the .claude/ directory if it doesn't exist. For each file below, skip if it already exists (unless the user approved overwriting in Step 1).
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 · 496 lines · 54 tokens per session scan A 6702a2641a23
bootstrap-project is a skill published in the GitHub repository jkm-4314/claude-code-skills (4 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 3,912 once invoked, about $0.0002 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
git-workflow
Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
push-preflight
Secret-scans the commits a git push would send (gitleaks + regex layer; never history), then checks clean tree, forbidden files and fast-forward, with size and open-issue advisories. Refuses on any secret hit, no bypass. Triggers on: push to origin, push to github, push to remote, git push, can we push, safe to push…
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.