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 Stepkar2004/init-configurator --skill bootstrapgit clone --depth 1 https://github.com/Stepkar2004/init-configuratorWrote 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/stepkar2004/init-configurator/bootstrap)<a href="https://agentmods.dev/skills/stepkar2004/init-configurator/bootstrap"><img src="https://agentmods.dev/badge/skills/stepkar2004/init-configurator/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/stepkar2004/init-configurator/bootstrap"><img src="https://agentmods.dev/badge/skills/stepkar2004/init-configurator/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.00059 | $0.01410 |
| Opus 5.5 | $0.00024 | $0.00564 |
| Sonnet 5.5 | $0.00012 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bootstrap — phase 0, from idea (or existing repo) to provably-working tree
You are generating; the tool is verifying. Never hand-write what a maintained official creator emits, and never claim phase 0 is done until the gates say so.
Step 0 — existing code?
If the target folder already has code, run initc describe FIRST. It drafts a
project.yaml from what deterministic inspection finds (FILL_ME marks its gaps).
Review the draft with the user, fill the gaps, then continue from step 4. The old
design assumed the folder was empty; you must not.
Step 0b — the genome present?
If .claude/skills/ is missing the base skills (workflow, skill-manager, socials,
bootstrap), ask the user whether to install them: initc spawn . copies the packaged genome
(skills, standards, docs templates), additive and idempotent — anything it reports as
"kept" already existed and stays the user's. (Refreshing an existing child later,
initc spawn . --force updates existing skills to the base's version; docs and
standards stay untouched.) Merge kept files by hand only if the user asks. Declining is
fine — bootstrap works standalone.
Step 1 — the interview (short, concrete, every answer recorded)
Ask only what changes the outcome:
- Owner identity — the name and email for LICENSE, README, and package metadata.
Read it from
git config user.name/git config user.emailfirst and confirm; only ask outright when they are unset. This is the ONE place a specific human's name belongs — the skills and conventions stay generic ("the user"), so the base reads the same for whoever clones it. - Stack and version — language(s), one stack per folder.
- Package manager — per stack (see the stack reference for the default and why).
- Quality tools — baseline linter/typechecker/test-runner is assumed; then offer
the opt-in menu from references/quality-tools.md.
A menu, never a default. If the user names a better tool you don't know, that is an
evolveevent: adopt it AND update the reference in the same session. - Docs shape — mirrored
docs/tree, or README-only. - Env vars known now — anything the code will read goes into the contract today.
- Primary agent file — CLAUDE.md or AGENTS.md (the other becomes a one-line pointer). If the chosen file already exists with the user's own content, we APPEND a short marked pointer block and never overwrite it; a fresh repo gets the full constitution inline. Do not invade an existing constitution — it may be carefully tuned, and it costs the user's context budget on every prompt.
What ships with it
5 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.
- 2mo ago First seen · 115 lines · 59 tokens per session scan A 1688f13262f9
bootstrap is a skill published in the GitHub repository Stepkar2004/init-configurator (1 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 1,410 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
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…
wrap-up
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says "wrap up", "close this out", "what do I own now", "give me the summary", "recap the agent", or when the orchestrator routes…
ma-playbook
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
intl-expansion
International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.