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 manhvann/codexkit --skill plangit clone --depth 1 https://github.com/manhvann/codexkitWrote 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/manhvann/codexkit/plan)<a href="https://agentmods.dev/skills/manhvann/codexkit/plan"><img src="https://agentmods.dev/badge/skills/manhvann/codexkit/plan/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/manhvann/codexkit/plan"><img src="https://agentmods.dev/badge/skills/manhvann/codexkit/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.01331 |
| Opus 5.5 | $0.00014 | $0.00532 |
| Sonnet 5.5 | $0.00007 | $0.00266 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
ck:plan 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning
Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.
Default (No Arguments)
If invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent, ask the user to choose an operation:
| Operation | Description |
|---|---|
(default) |
Create implementation plan for a task |
archive |
Write journal entry & archive plans |
red-team |
Adversarial plan review |
validate |
Critical questions interview |
Present options with header "Planning Operation", question "What would you like to do?".
Workflow Modes
Default: --auto (analyze task complexity and auto-pick mode).
| Flag | Mode | Research | Red Team | Validation | Cook Flag |
|---|---|---|---|---|---|
--auto |
Auto-detect | Follows mode | Follows mode | Follows mode | Follows mode |
--fast |
Fast | Skip | Skip | Skip | --auto |
--hard |
Hard | 2 researchers | Yes | Optional | (none) |
--parallel |
Parallel | 2 researchers | Yes | Optional | --parallel |
--two |
Two approaches | 2+ researchers | After selection | After selection | (none) |
Add --no-tasks to skip task hydration in any mode.
Load: references/workflow-modes.md for auto-detection logic, per-mode workflows, context reminders.
When to Use
- Planning new feature implementations
- Architecting system designs
- Evaluating technical approaches
- Creating implementation roadmaps
- Breaking down complex requirements
Core Responsibilities & Rules
Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.
1. Research & Analysis
Load: references/research-phase.md
Skip if: Fast mode or provided with researcher reports
2. Codebase Understanding
Load: references/codebase-understanding.md
Skip if: Provided with scout reports
What ships with it
12 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/archive-workflow.md 2.4 KB
- references/codebase-understanding.md 2.0 KB
- references/output-standards.md 4.5 KB
- references/plan-organization.md 3.7 KB
- references/red-team-personas.md 2.6 KB
- references/red-team-workflow.md 2.6 KB
- references/research-phase.md 1.5 KB
- references/solution-design.md 2.0 KB
- references/task-management.md 5.5 KB
- references/validate-question-framework.md 2.3 KB
- references/validate-workflow.md 2.2 KB
- references/workflow-modes.md 5.6 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.
- 1mo ago First seen · 139 lines · 35 tokens per session scan A a86bb9cf1495
ck:plan is a skill published in the GitHub repository manhvann/codexkit (89 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,331 once invoked, about $0.0001 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…