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/fixnpx skills add manhvann/codexkit --skill fixgit 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.00037 | $0.01143 |
| Opus 5 | $0.00018 | $0.00571 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
ck:fix 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixing
Unified skill for fixing issues of any complexity with intelligent routing.
Arguments
--auto- Activate autonomous mode (default)--review- Activate human-in-the-loop review mode--quick- Activate quick mode--parallel- Activate parallel mode: route to parallelfullstack_developeragents per issue
Workflow
Step 1: Mode Selection
First action: If there is no "auto" keyword in the request, ask the user to determine workflow mode:
| Option | Recommend When | Behavior |
|---|---|---|
| Autonomous (default) | Simple/moderate issues | Auto-approve if score >= 9.5 & 0 critical |
| Human-in-the-loop Review | Critical/production code | Pause for approval at each step |
| Quick | Type errors, lint, trivial bugs | Fast debug → fix → review cycle |
See references/mode-selection.md for the mode-selection prompt format.
Step 2: Debug
- Activate
ck:debugskill. - Guess all possible root causes.
- Prefer multiple
Explore/scout agents in parallel to verify each hypothesis when the runtime exposes delegation; otherwise use parallel searches and report the limitation. - Create report with all findings for the next step.
Step 3: Complexity Assessment & Task Orchestration
Classify before routing. See references/complexity-assessment.md.
| Level | Indicators | Workflow |
|---|---|---|
| Simple | Single file, clear error, type/lint | references/workflow-quick.md |
| Moderate | Multi-file, root cause unclear | references/workflow-standard.md |
| Complex | System-wide, architecture impact | references/workflow-deep.md |
| Parallel | 2+ independent issues OR --parallel flag |
Parallel fullstack_developer agents |
Task Orchestration (Moderate+ only): After classifying, use available task-tracking tools for all phases upfront with dependencies. See references/task-orchestration.md.
- Skip for Quick workflow (< 3 steps, overhead exceeds benefit)
- Create tracked tasks with dependency chains when task tools exist
- Update task/checklist state as each phase completes
- For Parallel: create separate task trees per independent issue
What ships with it
14 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.
- references/complexity-assessment.md 2.3 KB
- references/mode-selection.md 1.2 KB
- references/parallel-exploration.md 3.6 KB
- references/review-cycle.md 2.3 KB
- references/skill-activation-matrix.md 3.2 KB
- references/task-orchestration.md 4.2 KB
- references/workflow-ci.md 680 B
- references/workflow-deep.md 4.6 KB
- references/workflow-logs.md 2.3 KB
- references/workflow-quick.md 1.6 KB
- references/workflow-standard.md 3.8 KB
- references/workflow-test.md 2.3 KB
- references/workflow-types.md 669 B
- references/workflow-ui.md 2.5 KB
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 · 112 lines · 37 tokens per session scan A 34ba9607eb34
ck:fix is a skill published in the GitHub repository manhvann/codexkit (88 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 1,143 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…