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 keefar/ticket-flow --skill kanbangit clone --depth 1 https://github.com/keefar/ticket-flowWrote 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/keefar/ticket-flow/kanban)<a href="https://agentmods.dev/skills/keefar/ticket-flow/kanban"><img src="https://agentmods.dev/badge/skills/keefar/ticket-flow/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/keefar/ticket-flow/kanban"><img src="https://agentmods.dev/badge/skills/keefar/ticket-flow/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.00052 | $0.01980 |
| Opus 5.5 | $0.00021 | $0.00792 |
| Sonnet 5.5 | $0.00010 | $0.00396 |
| Haiku 4.5 | $0.00005 | $0.00198 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban — tracker maintenance (beads)
All paths are relative to the project root (cwd / git rev-parse --show-toplevel):
Operational board (hot path): bd itself — Inbox · Backlog · In Progress · Testing, expressed as bd status + labels.
Strategic plan: ROADMAP.md — epics + later + parked. Cold path, only when strategically relevant.
Spec template: docs/specs/SPEC-TEMPLATE.md — template for item specs.
Static snapshot (on demand): /ticket-flow:board writes a read-only KANBAN.md from bd state — never a workflow input.
bd is the sole source of truth. The workflow never reads or writes
KANBAN.md — new items go straight to bd create, state moves via
bd-helper.sh. (The former KANBAN.md-backed Mode B was removed — tf is
beads-only; the dual-mode code is preserved at refs/archive/mode-kanban.)
Toolbox (skills/kanban/):
bd-helper.sh— sourced bypickup,finish,flow, and this skill. Exposesbd_id_for <kanban#>,bd_set_status,bd_update_notes_{append,replace_prefix,remove_prefix}. State transitions go throughbd_set_status(canonical inbox / backlog / in_progress / testing) plusbd closefor Done; notes edits go through the merge-safe wrappers (neverbd update --notes=directly — that's destructive).kanban-render.sh— generate the read-onlyKANBAN.mdsnapshot from bd state. Not part of any workflow skill — reachable only via/ticket-flow:board. See that skill.kanban-import.sh— one-shotKANBAN.md → beadsmigration: parse an existing board's rows into bd. Idempotent (skips kanban-N labels already in bd). Invoked by/ticket-flow:initwhen it finds a legacy KANBAN.md, not in the steady-state workflow.
Workflow commands (Ticket-Flow)
| Command | Phase | Effect |
|---|---|---|
/ticket-flow:spec <id> |
Pre-Backlog | Create a spec doc from template, set note to spec: drafting (or a full autonomous draft with --auto, note → spec: review) |
/ticket-flow:pickup <id> |
Phase 1 | Worktree + branch lock + move to In Progress |
/ticket-flow:implement |
Phase 2 | Execute the plan (interactive or subagent dispatch) |
/ticket-flow:finish |
Phase 3 | Review + deploy + merge + move to Testing |
/ticket-flow:flow <id> |
Orchestrator | Phase 1 → 2 → 3, --local with checkpoints, --serial --loop unattended |
What ships with it
4 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 First seen · 136 lines · 52 tokens per session scan A e00f9acd8e7f
kanban is a skill published in the GitHub repository keefar/ticket-flow (4 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,980 once invoked, about $0.0002 per session on Opus 5.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
flow-next-flow
Use first in a Flow-Next repo for a spec id, change, bug, issue, slow code or metric, cleanup, design fork, dump to explain, repeated mistake, prompt change, what could break, what next. No quick asks.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next
Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).
project-discuss
A project-discussion management workflow that keeps track of decisions, open questions, project context, and incidents. It uses a project's cadence files, which are shared records for ongoing discussions and decisions.
subtask-update
Update subtask with fixes or new steps. Two trigger modes: (A) Auto-called by autoworker:gate-check on FAIL — reads FAIL info, adds supplementary steps. (B) User calls with a finding/bug during testing — diagnoses, fixes, updates subtask. Both modes end by invoking autoworker:dispatch to re-enter the loop.