Borrowing it
Nothing to install: this file belongs to MichiBl/Claude-Code-Default-Repo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MichiBl/Claude-Code-Default-Repo/main/.claude/skills/bootstrap/SKILL.mdgit clone --depth 1 https://github.com/MichiBl/Claude-Code-Default-RepoWrote 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/michibl/claude-code-default-repo/bootstrap)<a href="https://agentmods.dev/skills/michibl/claude-code-default-repo/bootstrap"><img src="https://agentmods.dev/badge/skills/michibl/claude-code-default-repo/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/michibl/claude-code-default-repo/bootstrap"><img src="https://agentmods.dev/badge/skills/michibl/claude-code-default-repo/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.00090 | $0.00915 |
| Opus 5.5 | $0.00036 | $0.00366 |
| Sonnet 5.5 | $0.00018 | $0.00183 |
| Haiku 4.5 | $0.00009 | $0.00092 |
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 2mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bootstrap — Gate-Infrastruktur für neue Projekte
Du richtest die minimale Infrastruktur ein, die die Qualitäts-Gates
dieses Setups brauchen: einen Linter, einen Test-Runner mit mindestens einem
echten Test, und die passende CI. Ziel ist ein Zustand, in dem verify.sh
tatsächlich prüft (statt mangels Tooling still grün zu sein) und die
/feature-Pipeline ihre Preconditions erfüllt sieht.
Minimal heißt minimal: kein Framework-Scaffolding, keine Beispiel-App, keine Dependencies über Linter + Test-Runner hinaus.
Workflow
1. Stack bestimmen
Nimm das Argument (node, python, …), sonst erkenne den Stack an
vorhandenen Dateien (package.json -> Node, pyproject.toml /
requirements.txt -> Python). Ist beides nicht eindeutig, frage den User
per AskUserQuestion.
2. Gates einrichten
Prüfe zuerst, was schon existiert — ergänze nur Fehlendes, überschreibe nie vorhandene Konfiguration.
Node:
package.json(falls fehlend:npm init -y, dann Felder aufräumen).- ESLint als Dev-Dependency + minimale Flat-Config;
"lint"-Script. - Vitest (oder der im Projekt schon vorhandene Runner) als Dev-Dependency;
"test"-Script. - Bei TypeScript-Projekten:
typescript+ minimalestsconfig.json. - Ein Smoke-Test unter
src/bzw.tests/, der etwas Echtes prüft (z. B. ein exportiertes Utility) — keinexpect(true).toBe(true).
Python (uv):
pyproject.toml(falls fehlend:uv init),ruffundpytestin die Dev-Dependencies (uv add --dev ruff pytest),uv.lockcommitten.tests/test_smoke.pymit einem echten Assert gegen Projektcode.
Anderer Stack (Go, Rust, …):
- Richte die nativen Werkzeuge ein (z. B.
go vet+go test,cargo clippy+cargo test). - Lege ein ausführbares
.claude/hooks/verify-project.shan, das sie ausführt — Vertrag: exit 0 = grün, exit 2 + Befund auf stderr = Claude muss nachbessern. Existiert diese Datei, führtverify.shnur sie aus.
3. CI aktivieren
Liegt unter .github/workflows/ ein passendes Example
(ci-node.yml.example / ci-python-uv.yml.example /
ci-python-pip.yml.example), benenne es nach ci.yml
um und passe es an die eingerichteten Befehle an. Für andere Stacks: kurz
anbieten, eine ci.yml zu schreiben — nicht ungefragt erfinden.
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.
- 2mo ago First seen · 75 lines · 90 tokens per session scan A 74973a89251c
bootstrap is a skill published in the GitHub repository MichiBl/Claude-Code-Default-Repo (2 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 915 once invoked, about $0.0004 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
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
testing-and-ci
Choose and run unit, E2E, Caddyfile fixture, automation, and CI checks for caddy-security. Use for coverage requirements, test evidence, failures, and report workflows; official OP conformance remains opt-in.