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 gablabelle/mcp-kanban --skill kanban-workgit 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-work)<a href="https://agentmods.dev/skills/gablabelle/mcp-kanban/kanban-work"><img src="https://agentmods.dev/badge/skills/gablabelle/mcp-kanban/kanban-work/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-work"><img src="https://agentmods.dev/badge/skills/gablabelle/mcp-kanban/kanban-work.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.00900 |
| Opus 5 | $0.00023 | $0.00450 |
| Sonnet 5 | $0.00009 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
kanban-work 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 12d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Through Kanban Tickets
You are executing planned work from the mcp-kanban board. Move tickets through columns and update them as you work.
Step 0: Start the board (MANDATORY FIRST STEP)
You MUST call mcp__kanban__open_board FIRST, before any other kanban tool. This starts the web UI server. Wait for it to return, then open the URL in the browser:
open "<url from open_board>"
Do NOT call any other kanban tool until this step is complete.
Step 1: Discover the board
Use mcp__kanban__list_columns to get the column IDs. Identify:
- The "in progress" column (for active work)
- The "review" column (if it exists, for completed-but-not-verified work)
- The "done" column (for finished work)
Use mcp__kanban__list_tickets to see all tickets and find which ones are ready to work on (in Backlog or Todo).
Step 2: Pick the next ticket
If $ARGUMENTS specifies a ticket or story, start with that. Otherwise, pick the highest-priority story that hasn't been started yet.
Use mcp__kanban__get_ticket to read the full ticket details including subtasks.
Step 3: Move the story to In Progress
Use mcp__kanban__move_ticket to move the parent story to the "in progress" column. This signals on the board that work has begun.
Step 4: Work through each subtask
For each subtask in the story:
- Before starting: Move the subtask to "in progress" with
mcp__kanban__move_ticket - Do the work: Implement the changes — read files, write code, run tests, etc.
- Update the ticket: Use
mcp__kanban__update_ticketto add implementation notes to the subtask description — what was done, what files were changed, any decisions made - Mark complete: Use
mcp__kanban__complete_subtaskto move the subtask to Done
Step 5: Complete the story
Once all subtasks are done:
- Use
mcp__kanban__update_ticketto update the parent story's description with a summary of what was implemented - Move the story to "review" or "done" column with
mcp__kanban__move_ticket
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.
- 12d ago First seen · 70 lines · 46 tokens per session scan A 12c444d64d17
kanban-work is a skill published in the GitHub repository gablabelle/mcp-kanban (3 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 900 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.