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/manhvann/codexkit/bootstrapnpx skills add manhvann/codexkit --skill bootstrapgit clone --depth 1 https://github.com/manhvann/codexkitWhat 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.00040 | $0.00949 |
| Opus 5 | $0.00020 | $0.00475 |
| Sonnet 5 | $0.00008 | $0.00190 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
ck: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 2d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap - New Project Scaffolding
End-to-end project bootstrapping from idea to running code.
Principles: YAGNI, KISS, DRY | Token efficiency | Concise reports
Usage
$bootstrap <user-requirements>
Flags (optional, default --auto):
| Flag | Mode | Thinking | User Gates | Planning Skill | Cook Skill |
|---|---|---|---|---|---|
--full |
Full interactive | Ultrathink | Every phase | --hard |
(interactive) |
--auto |
Automatic | Ultrathink | Design only | --auto |
--auto |
--fast |
Quick | Think hard | None | --fast |
--auto |
--parallel |
Multi-agent | Ultrathink | Design only | --parallel |
--parallel |
Example:
$bootstrap "Build a SaaS dashboard with auth" --fast
$bootstrap "E-commerce platform with Stripe" --parallel
Workflow Overview
[Git Init] → [Research?] → [Tech Stack?] → [Design?] → [Planning] → [Implementation] → [Test] → [Review] → [Docs] → [Onboard] → [Final]
Each mode loads a specific workflow reference + shared phases.
Mode Detection
If no flag provided, default to --auto.
Load the appropriate workflow reference:
--full: Loadreferences/workflow-full.md--auto: Loadreferences/workflow-auto.md--fast: Loadreferences/workflow-fast.md--parallel: Loadreferences/workflow-parallel.md
All modes share: Load references/shared-phases.md for implementation through final report.
Step 0: Git Init (ALL modes)
Check if Git initialized. If not:
--full: Ask user if they want to init →git_managersubagent (mainbranch)- Others: Auto-init via
git_managersubagent (mainbranch)
Skill Triggers (MANDATORY)
After early phases (research, tech stack, design), trigger downstream skills:
Planning Phase
Activate ck:plan skill with mode-appropriate flag:
--full→ck:plan --hard <requirements>(thorough research + validation)--auto→ck:plan --auto <requirements>(auto-detect complexity)--fast→ck:plan --fast <requirements>(skip research)--parallel→ck:plan --parallel <requirements>(file ownership + dependency graph)
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.
- 2d ago First seen · 102 lines · 40 tokens per session scan A 8b0b167d00fb
ck:bootstrap is a skill published in the GitHub repository manhvann/codexkit (88 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 949 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…