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 JansenAnalytics/claudex --skill kanban-agentgit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/kanban-agent)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/kanban-agent"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/kanban-agent.svg" alt="Measured on agentmods" 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.00049 | $0.00788 |
| Opus 5 | $0.00024 | $0.00394 |
| Sonnet 5 | $0.00010 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
kanban-agent 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 3d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban Agent Skill
Overview
Persistent task board backed by SQLite. Survives across sessions. Supports priorities (p0-p3), statuses (backlog → todo → in-progress → review → done), deadlines, dependencies, projects, tags, and full history logging.
Script
node ${CLAUDE_SKILLS_DIR:-$HOME/.claude-agent/.claude/skills}/kanban-agent/scripts/kanban.cjs <command> [args]
Commands
Task Management
kanban add "title" [--desc "..."] [--priority p0-p3] [--project X] [--tags "a,b"] [--deadline YYYY-MM-DD] [--depends 1,2] [--status STATUS]
kanban update <id> [--title "..."] [--desc "..."] [--priority p0-p3] [--project X] [--tags "a,b"] [--deadline YYYY-MM-DD] [--note "..."]
kanban move <id> <backlog|todo|in-progress|review|done|blocked|cancelled>
kanban done <id> [--note "completion note"]
kanban block <id> --reason "why"
kanban unblock <id>
kanban delete <id>
Viewing
kanban list [--status todo,in-progress] [--priority p0,p1] [--project X] [--tag work] [--flat] [--limit N]
kanban show <id> — full detail + dependencies + history
kanban search "query" — search title, description, notes, tags
kanban deps <id> — dependency tree
kanban overdue — tasks past deadline
Reports
kanban standup [--days 1] — daily standup (completed, in-progress, blocked, up next)
kanban projects — project progress bars
kanban stats — overall statistics
kanban export [--format json|markdown]
Agent Behavior
Auto-creating tasks
When the user mentions something to do, track, or remember — create a task:
node kanban.cjs add "Wire onTokenSelect in Market Dashboard" --project brewboard --priority p2 --tags "frontend"
During heartbeats
Run kanban standup to check what's active, blocked, or overdue. Report anything urgent.
Completing work
After finishing a task, mark it done:
node kanban.cjs done 5 --note "Implemented and tested"
Priority Guide
- p0 🔴 Critical — blocking the user or production
- p1 🟠 High — should do today/tomorrow
- p2 🟡 Normal — this week
- p3 ⚪ Nice-to-have — when time permits
What ships with it
1 file 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.
- 3d ago First seen · 89 lines · 49 tokens per session scan A 676f0aecb892
kanban-agent is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 788 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-09-03.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
kanban-board
A Kanban board is a visual task list with columns for stages such as To do, In progress, In review, and Done. It can show filters, labels, due dates, assignees, comments, and swimlanes that group cards.
kanban-tui
Comprehensive kanban board and task management via ktui CLI. Use for project tracking, todo lists, task dependencies, workflow automation, and board management. Activates when user mentions boards, tasks, kanban, or project management. If the ktui command is not available, but uv is available utilize uvx kanban-tui…
gr-product-dev-ops
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified…
team-motivation-ops
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict…
kanban-orchestrator
Kanban orchestrator: decompose, route, verify. No executing.