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 agentmods add skills/keefar/ticket-flow/boardnpx skills add keefar/ticket-flow --skill boardgit clone --depth 1 https://github.com/keefar/ticket-flowWhat 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 | $0.00053 | $0.00875 |
| Opus 5 | $0.00026 | $0.00438 |
| Sonnet 5 | $0.00011 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
board 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ticket-flow:board — Static board snapshot from bd
Args: none (default — write KANBAN.md) · --stdout (print to stdout, no write) · --check (exit 1 if the current KANBAN.md drifts from bd state)
What it does
In beads mode (mode=beads) the workflow is pure bd — no skill reads or
writes KANBAN.md. The Dolt DB under .beads/ is not glanceable, so this
skill produces a static, git-diffable, GitHub-viewable board snapshot from
the current bd state on demand.
This is the only place KANBAN.md is generated in beads mode. It is:
- Manual — you run it; no other skill ever does.
- Opt-in — beads mode works completely without it.
- Read-only w.r.t. the workflow — the snapshot is an output, never an
input.
/ticket-flow:spec,/pickup,/finish,/flow, and/kanbando not read the file it writes. Editing the snapshot has no effect; change bd, then re-run/ticket-flow:board.
For a live board, npx beads-ui start is the alternative (see
docs/research/kanban-visualization.md); /ticket-flow:board is the
git-committable static counterpart.
When to use
- Before a commit, when you want a board snapshot tracked in git history.
- To share a glanceable board on GitHub without giving viewers
bd. - Ad-hoc, whenever you want a markdown view of the current bd state.
Do not wire it into a workflow — that is exactly the in-workflow rendering
that spec #23 removed. If you find yourself running it after every state
change, use beads-ui for the live view instead.
Prerequisites
- A beads project (
.beads/present). A leftovermode=kanbanflag makesbd_moderefuse with a migration pointer. bdandjqonPATH.
Steps
-
Confirm bd is usable. Source
skills/kanban/bd-helper.shand check:source "${CLAUDE_PLUGIN_ROOT}/skills/kanban/bd-helper.sh" bd_available || { echo "no usable beads tracker here" >&2; exit 1; } -
Run the renderer.
kanban-render.shdoes the work (groups bd issues into the four columns, emits markdown). Forward the arg:
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 · 81 lines · 53 tokens per session scan A 7d2336815505
board is a skill published in the GitHub repository keefar/ticket-flow (4 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 875 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-31.
Other skills, from other repositories
project-discuss
⚠️ 本 skill 与 brainstorming / writing-plans / executing-plans 等流程 skill 正交、可并行触发，不互斥。 已调用流程 skill 不等于可以跳过本 skill；只要涉及项目讨论/决策/查询，都需要额外激活本 skill。 项目讨论管理协议。管理讨论上下文、决策记录、查询行为。 触发：用户讨论项目方向/设计/技术选型/需求分析/功能规划时； 用户问"我们讨论到哪了"/"XX 确定了吗"； 用户想修改已确定的内容；用户提供外部文档； 用户询问项目现状/架构/实现细节/历史决策（含 debug 揭示架构问题时）； 当 bug…
cadence-bootstrap
Use when starting any conversation in a cadence-managed project (project root contains cadence/INDEX.md or cadence/ACTIVE.md). Establishes cadence workflow conventions — 记 / 整 / 查 三阶段记录协议, ACTIVE.md / INDEX.md state contract, domain-neutral adaptive recording fidelity, session start behaviors, and subagent dispatch…
cadence-resume
继续之前某次 session 的讨论上下文(v0.4:Step 6 archive cleanup B1 修复 + contenthashes 判据 + 派 retriever 替代 auditor)。用户说 '继续上次'/'resume' 或跑 /cadence-resume 时触发。.
cadence-handoff
整理当前 session 讨论内容到 cadence 档案(v0.4:触发整 阶段（ε 整合）兜底 + 写 sha1 书签式 snapshot,15-30 行)。用户说 'handoff'/'整理 session'/'换新 session' 或跑 /cadence-handoff 时触发。.
cadence-init
初始化 cadence 工作流目录结构。支持两种模式：新项目（极简模板 + TBD 占位） 和已有项目（通用发现 + 领域适配扫描 + 来源不一致清单）。适用于软件、研究、 写作、学习、运营及其他项目。当用户说"初始化 cadence"、 "开始用 cadence"、或跑 /cadence-init slash command 时触发。.
polish
Polish a completed code change with a bounded independent review protocol. Use after implementation and before final approval or PR to review intent, acceptance criteria, non-goals, diff, relevant files, verification, and previously rejected findings.