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/project-managementnpx skills add manhvann/codexkit --skill project-managementgit 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.00041 | $0.01002 |
| Opus 5 | $0.00020 | $0.00501 |
| Sonnet 5 | $0.00008 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
ck:project-management 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Management
Project oversight and coordination using runtime task tools with persistent plan files.
Principles: Token efficiency | Concise reports | Data-driven insights
When to Use
- Checking project status or progress across plans
- Updating plan statuses after feature completion
- Hydrating/syncing Codex tasks with plan files
- Generating status reports or summaries
- Coordinating documentation updates after milestones
- Verifying task completeness against acceptance criteria
- Cross-session resume of multi-phase work
Core Capabilities
1. Task Operations
Load: references/task-operations.md
Use task tools when the runtime exposes them; otherwise keep checklist state in plan files.
- Create tasks with metadata (phase, priority, effort, planDir, phaseFile)
- Track status:
pending→in_progress→completed - Manage dependencies with
addBlockedBy/addBlocks - Coordinate parallel agents with scoped ownership
2. Session Bridging (Hydration Pattern)
Load: references/hydration-workflow.md
Tasks are ephemeral. Plan files are persistent. The hydration pattern bridges them:
- Hydrate: Read plan
[ ]items → create one tracked task per unchecked item - Work: task/checklist updates track progress in real time
- Sync-back: Reconcile all completed tasks against all phase files, update
[ ]→[x], update YAML frontmatter status - Resume: Next session re-hydrates from remaining
[ ]items
3. Progress Tracking
Load: references/progress-tracking.md
- Scan the configured plans directory for active
plan.mdfiles - Parse YAML frontmatter for status, priority, effort
- Count
[x]vs[ ]in phase files for completion % - Cross-reference completed work against planned tasks
- Verify acceptance criteria met before marking complete
4. Documentation Coordination
Load: references/documentation-triggers.md
Trigger configured docs path updates when:
- Phase status changes, major features complete
- API contracts change, architecture decisions made
- Security patches applied, breaking changes occur
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 · 123 lines · 41 tokens per session scan A 2120f7e4c306
ck:project-management is a skill published in the GitHub repository manhvann/codexkit (88 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 1,002 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…