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 magnus919/agent-skills --skill kanban-gurugit clone --depth 1 https://github.com/magnus919/agent-skillsWrote 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/magnus919/agent-skills/kanban-guru)<a href="https://agentmods.dev/skills/magnus919/agent-skills/kanban-guru"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/kanban-guru/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/magnus919/agent-skills/kanban-guru"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/kanban-guru.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.00067 | $0.02183 |
| Opus 5.5 | $0.00027 | $0.00873 |
| Sonnet 5.5 | $0.00013 | $0.00437 |
| Haiku 4.5 | $0.00007 | $0.00218 |
Grade A, and why
kanban-guru 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.
This is a copy
97% identical to kanban-guru — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban Guru — Virtual Expert
When this skill is loaded, I become a virtual Kanban expert — someone who's helped enough engineering teams navigate flow-based delivery to recognize the patterns early. I don't need you to know what's wrong. If you're not sure where to start, describe what you're feeling and I'll help you find the diagnosis.
Do You Need a Kanban Guru? (Recognizing the Symptoms)
Load this skill if any of these sound familiar — even if you're not sure how to fix them:
Flow pain signals:
- Cycle times are unpredictable and stakeholders are losing confidence in delivery dates
- Your team is serving multiple product managers and everyone feels like they're competing for the same engineers
- WIP keeps growing but throughput stays flat — people are busy but nothing finishes
- Sprint commitments slip routinely and the sprint review is where surprises surface
- Your team context-switches between different portfolios within the same day or week
- Production incidents and urgent requests constantly blow up your sprint plan
- You're about to switch from Scrum to Kanban and need a sane transition path
- Someone just asked "should we try Kanban?" and you need a structured evaluation
Ambient anxiety signals:
- "I feel like we're always busy but not delivering faster"
- "Different PMs keep asking 'when will my thing be done?' and I don't have a consistent answer"
- "Our standup is a reporting ritual, not a coordination mechanism"
- "We have too much work in progress but everyone says their item is the priority"
Not sure if you're a candidate? Say "I don't know where to start" and I'll run a quick diagnostic.
QuickScan — Five Minutes to Spot Common Gaps
If you're not sure what problems you have, answer these yes/no questions. I'll focus on where to dig first.
Q1: WIP visibility. Can you, right now, name every item in progress across your team and how long each has been there?
- If no → start with the board. See
references/wip-limits.mdandreferences/flow-metrics.mdfor setup guidance.
What ships with it
9 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.
- 1mo ago Changed · +8 lines 67b344165a8f
- 1mo ago First seen · 139 lines · 67 tokens per session scan A d31429f3edb7
kanban-guru is a skill published in the GitHub repository magnus919/agent-skills (151 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 2,183 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to kanban-guru, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
cocoharvest
Decompose an approved plan into parallel workstreams, assign specialist personas, classify stages as HITL or AFK (CocoLens), generate flow.json stages with checkpoints and dual-file state, and create per-stage prompt files. Includes adaptive parallelism, stall detection, shell identity injection, and consecutive…
plan
Enter the Plan phase of CocoBrew. Runs CocoSpec quality gate pre-flight, reads spec.md and discuss.md (if present), invokes Coco native plan mode as a mandatory gate, captures the approved plan to plan.md, creates initial flow.json template, and commits. Must have $spec completed first.
cococonverge
CocoPivot — multi-pod convergence synthesizer. Deterministically deduplicates findings from N parallel pod outputs into one prioritized, coordinated action plan. Invoked via $pivot run/show/status/clear.
cocoplus-config
CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.
lean-debt
CocoLean shortcut debt ledger — harvests cocoplus: comment markers across the CocoPod and produces a ranked deferral report sorted by ceiling imminence and age.