Borrowing it
Nothing to install: this file belongs to antopolskiy/kanban-md. 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/antopolskiy/kanban-md/main/.agents/skills/kanban-based-development/SKILL.mdgit clone --depth 1 https://github.com/antopolskiy/kanban-mdWrote 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/antopolskiy/kanban-md/kanban-based-development)<a href="https://agentmods.dev/skills/antopolskiy/kanban-md/kanban-based-development"><img src="https://agentmods.dev/badge/skills/antopolskiy/kanban-md/kanban-based-development/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/antopolskiy/kanban-md/kanban-based-development"><img src="https://agentmods.dev/badge/skills/antopolskiy/kanban-md/kanban-based-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.02253 |
| Opus 5 | $0.00034 | $0.01126 |
| Sonnet 5 | $0.00014 | $0.00451 |
| Haiku 4.5 | $0.00007 | $0.00225 |
Grade A, and why
kanban-based-development 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban-Based Development
Autonomous, parallel-safe development using kanban-md to coordinate work on a shared board.
Claims prevent duplicate work; review is the waiting room (handoff, user action, merge, decisions).
Multi-Agent Environment
This board is shared. Multiple agents and humans may be working on it simultaneously. You are NOT the only one reading or modifying tasks. This means:
- Another agent may claim a task between the time you list it and try to pick it.
- Tasks you saw as available a moment ago may no longer be available.
The claim mechanic is the coordination primitive. It prevents two agents from working on the same task. You MUST claim a task before starting any work on it, and you MUST only pick unclaimed tasks. Violating this causes duplicate work, merge conflicts, and wasted effort.
Non-Negotiables
- Claim before you change anything. No task edits, no code changes.
- One active task per agent. Keep at most one task in
in-progressfor your agent session. - Never steal a live claim. If it's claimed, pick something else.
- Never release someone else’s claim. Only use
edit --releasefor your own work (or when the user explicitly asks). - Always leave a handoff. Before you park a task, write a short update in the body so someone else can continue.
- Refresh claims to avoid timeout. If the task might take longer than
claim_timeout, periodically renew your claim:kanban-md edit <ID> --claim <agent>.
Board Home vs Worktrees (simple rule)
- Always run
kanban-mdfrom board home (the canonical repo directory that owns the shared board). - Always do code changes in a task worktree. Never edit code in board home.
- If the board is git-tracked, commit board changes on
mainas a separate commit after the task is merged and moved todone.
At the start of the session, determine and remember <board-home>:
cd <the canonical repo directory that owns the shared board>
pwd # remember this path as <board-home>
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 · 265 lines · 68 tokens per session scan A f2a40ae9b4fc
kanban-based-development is a skill published in the GitHub repository antopolskiy/kanban-md (215 stars, last pushed 18d ago), licensed MIT. It adds 68 tokens to every session and 2,253 once invoked, about $0.0003 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-30.
Other skills, from other repositories
rmine
Reference for the rmine CLI (Redmine client) — issue, time-tracking, and project commands, filter/name-matching semantics, and profile handling. Use when the user asks about Redmine issues, tickets, time logging, or projects.
ntm
Run NTM for multi-agent tmux orchestration, work triage, robot mode, safety, coordination, and local APIs. Use when spawning swarms, dispatching work, or operating ntm as an agent or human operator.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
linear-graphql-skill
Operate Linear workspace issues, projects, and teams through Linear GraphQL API using UXC. Use when tasks require querying or creating issues, managing projects, or interacting with Linear workflow. Supports both Personal API Key and OAuth authentication.
genie-orca-wish
Turn a brainstorm/design into an APPROVED-able wish whose Dispatch plan is the literal input to Orca tasks and Linear issues. High-reasoning pass: pre-decide everything so fast workers can execute without judgment calls.