Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Xakki/ai-agents-skills/plugin install ai-agents-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/xakki/ai-agents-skills/kanban)<a href="https://agentmods.dev/skills/xakki/ai-agents-skills/kanban"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/kanban/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/xakki/ai-agents-skills/kanban"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/kanban.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.00025 | $0.03582 |
| Opus 5 | $0.00013 | $0.01791 |
| Sonnet 5 | $0.00005 | $0.00716 |
| Haiku 4.5 | $0.00003 | $0.00358 |
Grade A, and why
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 11d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stages
| Stage | Path | Description |
|---|---|---|
| Grooming | .claude/kanban/grooming/ |
Draft tasks with open questions / unresolved scope |
| Todo | .claude/kanban/todo/ |
Refined tasks ready to start |
| Progress | .claude/kanban/progress/ |
Currently being worked on |
| Test | .claude/kanban/test/ |
Implementation handed off; review/QA in progress |
| Ready | .claude/kanban/ready/ |
Auto-review passed; awaiting authorized finalization |
| Done | .claude/kanban/done/ |
Authorized completion |
Lifecycle: grooming → todo → progress → test → ready → done.
grooming/ and ready/ are agent-boundary stages: autonomous runs never enter grooming/
and never advance past ready/, except an EPIC with recorded EPIC-scoped upfront
autonomous authorization as defined in Done below.
IDs & Prefix
Every card carries <PREFIX>-<NUM> (epic subtasks: <PREFIX>-<NUM>-<NN>, see
Epics below). Counters live in <repo>/.claude/kanban.lock (git-committed,
flock-guarded, reconciled against cards actually on the board on every
allocation — a stale counter after a merge can't hand out a duplicate ID).
First use in a project (no prefix= yet) is a confirmation, never a
guess. kanban-id.sh next/prefix exits 2 with the board's candidate
prefixes (existing board cards win by count if any, else a dir-name-derived
one) — on that exit, ask the user which to use (AskUserQuestion,
candidates as options, recommended one first) and then run
kanban-id.sh set-prefix <PREFIX> to confirm it; don't auto-pick and don't
retry silently. Full mechanics, lock format, prefix registry →
scripts.md.
Scripts
Set ROOT="${AI_AGENTS_SKILLS_ROOT:-${CLAUDE_PLUGIN_ROOT:-${PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-}}}}" and
S="$ROOT/skills/kanban/scripts", then invoke every script below as "$S"/<name> — never by bare name
(optional leading --repo <path>, default git toplevel):
What ships with it
22 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.
- reference.md 5.1 KB
- scripts.md 14 KB
- scripts/kanban-id.sh 3.8 KB runs code
- scripts/kanban-lib.sh 19 KB runs code
- scripts/kanban-lint.sh 5.5 KB runs code
- scripts/kanban-move.sh 5.1 KB runs code
- scripts/kanban-new.sh 5.0 KB runs code
- scripts/kanban-status.sh 3.5 KB runs code
- task-template.md 1.3 KB
- test/exitcodes.test.sh 3.0 KB runs code
- test/id-basics.test.sh 2.6 KB runs code
- test/id-concurrency.test.sh 1.1 KB runs code
- test/id-lock-gitignore.test.sh 2.7 KB runs code
- test/id-prefix-confirm.test.sh 4.8 KB runs code
- test/id-prefix-legacy-board.test.sh 6.2 KB runs code
- test/id-reconcile.test.sh 1.2 KB runs code
- test/id-sub.test.sh 1.3 KB runs code
- test/lint.test.sh 5.5 KB runs code
- test/move.test.sh 5.4 KB runs code
- test/new.test.sh 3.5 KB runs code
- test/run-all.sh 250 B runs code
- test/status.test.sh 1.2 KB runs code
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.
- 11d ago First seen · 232 lines · 25 tokens per session scan A 48fb1d19701f
kanban is a skill published in the GitHub repository Xakki/ai-agents-skills (6 stars, last pushed 20d ago), licensed MIT. It adds 25 tokens to every session and 3,582 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-31.
Other skills, from other repositories
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
specs
Use when a rough user story, bug report, feature idea, piece of feedback, or an implementation plan should be recorded as a GitHub issue — "file a ticket for this", "open an issue", "write this up for the backlog", "we should track this", "log this bug", "spec this out as a ticket so we can pick it up later" — i.e.…
ag-pipeline-issue
Pipeline Issue→SPEC→Build→Verify→Test. Toda GitHub Issue gera SPEC antes de implementar, e toda implementacao e verificada contra a SPEC e testada. Use when starting work on a GitHub Issue.
ag-team-terminais
Protocolo para 2+ sessoes Claude interativas em terminais separados trabalharem no MESMO repo com objetivos distintos. Coordenador + workers, manifesto duravel em docs/ai-state/team/, mensagens nativas via ListAgents/SendMessage, worktree por worker. Modos: init | join | status | fechar. Para teammates dentro de UMA…
ag-registrar-issue
Registra GitHub Issues para problemas nao resolvidos imediatamente. Recebe contexto via SendMessage de outros agents. Dedup, labels, severidade. Use when an agent finds a problem it cannot fix now.
ag-teleportar
Switch rapido entre projetos no workspace com contexto preservado. Carrega CLAUDE.md, detecta stack, verifica .env, mostra branch atual, e resume estado. Nao e cd — e context-aware switching.