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/kanbannpx skills add manhvann/codexkit --skill kanbangit 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.00017 | $0.00659 |
| Opus 5 | $0.00009 | $0.00329 |
| Sonnet 5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
ck:kanban 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plans Dashboard
Plans dashboard with progress tracking and timeline visualization.
Usage
ck:kanban- View dashboard for the configured plans directoryck:kanban <dir>- View dashboard for specific directoryck:kanban --stop- Stop running server
Features
- Plan cards with progress bars
- Phase status breakdown (completed, in-progress, pending)
- Timeline/Gantt visualization
- Activity heatmap
- Issue and branch links
Execution
IMPORTANT: Run the server as a background command when the runtime supports it, so it remains manageable from the active session.
The skill is located at .agents/skills/plans-kanban/.
Stop Server
If --stop flag is provided:
node .agents/skills/plans-kanban/scripts/server.cjs --stop
Start Server
Otherwise, run the kanban server with --foreground flag so the process stays alive:
# Determine plans directory
INPUT_DIR="$1"
PLANS_DIR="${INPUT_DIR:-${CK_PLANS_PATH:-plans}}"
# Start kanban dashboard
node .agents/skills/plans-kanban/scripts/server.cjs \
--dir "$PLANS_DIR" \
--host 0.0.0.0 \
--open \
--foreground
Critical: When calling the Bash tool:
- Set
run_in_background: truewhen the shell tool supports background processes - Set
timeout: 300000(5 minutes) to prevent premature termination - Parse JSON output and report URL to user
Example Bash tool call:
{
"command": "node .agents/skills/plans-kanban/scripts/server.cjs --dir \"${CK_PLANS_PATH:-plans}\" --host 0.0.0.0 --open --foreground",
"run_in_background": true,
"timeout": 300000,
"description": "Start kanban server in background"
}
After starting, parse the JSON output and report:
- Local URL for browser access
- Network URL for remote device access (if available)
- Inform user that server is now running in the background when supported
CRITICAL: MUST display the FULL URL including path and query string. NEVER truncate to just host:port.
Future Plans
The ck:kanban command will evolve into VibeKanban-inspired AI agent orchestration:
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 · 100 lines · 17 tokens per session scan A 33b93b786105
ck:kanban is a skill published in the GitHub repository manhvann/codexkit (88 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 659 once invoked, about $0.0001 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
bmad-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".