Borrowing it
Nothing to install: this file belongs to gablabelle/mcp-kanban. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gablabelle/mcp-kanban/main/.claude/skills/kanban-plan/SKILL.mdgit clone --depth 1 https://github.com/gablabelle/mcp-kanbanWrote 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/gablabelle/mcp-kanban/kanban-plan)<a href="https://agentmods.dev/skills/gablabelle/mcp-kanban/kanban-plan"><img src="https://agentmods.dev/badge/skills/gablabelle/mcp-kanban/kanban-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/gablabelle/mcp-kanban/kanban-plan"><img src="https://agentmods.dev/badge/skills/gablabelle/mcp-kanban/kanban-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00046 | $0.00736 |
| Opus 5.5 | $0.00018 | $0.00294 |
| Sonnet 5.5 | $0.00009 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
kanban-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 2mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Work on the Kanban Board
You are planning work by breaking it into stories and subtasks on the mcp-kanban board.
Step 1: Open the board immediately
Open the Kanban board in the browser so the user can watch tickets appear in real-time:
open "http://localhost:$(cat ~/.mcp-kanban/config.json 2>/dev/null | jq -r '.port // 3010')"
Step 2: Discover the board structure
Use mcp__mcp-kanban__list_columns to get the available columns and their IDs. Identify which column is best for new planned work (typically "Backlog" or "Todo").
Use mcp__mcp-kanban__list_tickets to check for existing tickets so you don't create duplicates.
Step 3: Analyze the work
Read relevant code files to understand the current state. Break the work described in $ARGUMENTS into:
- Stories: High-level features or logical units of work. Each story should be independently deliverable.
- Subtasks: Concrete, actionable implementation steps under each story. Each subtask should be completable in a single focused session.
Step 4: Create tickets on the board
For each story:
- Create a story ticket with
mcp__mcp-kanban__create_ticket— use a clear title and a description that explains the goal, acceptance criteria, and any relevant technical context - Create subtasks under it with
mcp__mcp-kanban__create_subtask— each subtask should have a concise title and a description covering what specifically needs to be done
Place stories in the "Backlog" or "Todo" column (whichever makes more sense given the board's column structure).
Set appropriate priorities: urgent for blockers, high for critical path items, medium for standard work, low for nice-to-haves.
Step 5: Present the plan and ask to start
After all tickets are created, present a summary:
- Total number of stories and subtasks created
- Brief overview of each story and its subtasks
- Suggested order of execution
Then ask the user: "The plan is on the board. Would you like me to start working through these tickets?"
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.
- 2mo ago First seen · 61 lines · 46 tokens per session scan A 385daee8943d
kanban-plan is a skill published in the GitHub repository gablabelle/mcp-kanban (4 stars, last pushed 8mo ago), licensed MIT. It adds 46 tokens to every session and 736 once invoked, about $0.0002 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-31.
kanban-plan compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| kanban-plangablabelle/mcp-kanban | Skill | 4 | 8mo ago | MIT | A | 46 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |