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/statusnpx skills add keefar/ticket-flow --skill statusgit 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.00095 | $0.01803 |
| Opus 5 | $0.00048 | $0.00901 |
| Sonnet 5 | $0.00019 | $0.00361 |
| Haiku 4.5 | $0.00010 | $0.00180 |
Grade A, and why
status 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 2d 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.
/ticket-flow:status — Project diagnostic + recommendation
Args: none — operates on the current working directory.
What it does
One-shot orientation: tells you what state this project is in and what to do next. Useful after compaction, when picking up someone else's branch, or before any /ticket-flow:flow to confirm the project is ready.
Companion to (not replacement for) the two diagnostics below it: bd doctor checks beads internals, Claude Code's built-in /doctor checks the harness (hooks, MCP servers, permissions, plugin loading), and /ticket-flow:status checks the project's tf-workflow state. The script points at both so a harness-level fault is not mistaken for an idle project.
Output
Single block of structured text:
ticket-flow @ <cwd> (branch: <git-branch>)
PROJECT BACKEND: beads | UNMIGRATED (legacy mode=kanban) | none — no scaffolding yet
SCAFFOLDING: git · .beads/ · SPEC-TEMPLATE.md · CLAUDE.md · AGENTS.md (✓ present / ✗ missing)
MEMORY HYGIENE: ✓ clean | ⚠ anti-MEMORY clause in <files>
IN-FLIGHT: N worktree(s) under .claude/worktrees
<path> (idle: <duration>) — time since the branch's last commit, mtime fallback if none yet
BEADS: <total> total · <open> open · <blocked> blocked · <ready> ready · <in_progress> in_progress
BRANCH LOCKS: N
<bd-id> -> <branch> (age: <duration>, in_progress since <ISO timestamp>)
UNCOMMITTED: clean | N files
RECOMMENDED NEXT STEPS:
- <ordered concrete commands>
NO ACTION NEEDED:
- <what's already clean>
Age and idle time are display-only (ticket-flow-76v): no threshold anywhere in the script turns a duration into an action — no branch delete, no lock release, no agent declared dead. "Branch lock age" comes from bd's own started_at on the in_progress bead (set the instant /ticket-flow:pickup step 5 claims it, right before it writes the branch: note); "worktree idle" comes from the seconds since that branch's last commit, falling back to the directory's mtime when there are no commits yet. TICKET_FLOW_NOW=<epoch-seconds> overrides "now" for both — tests only.
What ships with it
6 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.
- 2d ago First seen · 89 lines · 95 tokens per session scan A fc8affd43bd6
status is a skill published in the GitHub repository keefar/ticket-flow (4 stars, last pushed 6d ago), licensed MIT. It adds 95 tokens to every session and 1,803 once invoked, about $0.0005 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
kanvibe-release-deploy
Use this skill whenever releasing or deploying KanVibe desktop from a clean, up-to-date dev checkout: ask only for the target version and release-note approval, then let the AI update package versions, run pnpm run deploy, publish the DMG GitHub release, update the Homebrew cask, create the release PR, and auto-merge…
council-router
Route code reviews to appropriate council members. Use when reviewing PRs, architecture decisions, or significant code changes that need expert perspective.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
taiyi-ultrawork
TaiyiForge ultrawork — 并行切片 + Cursor Task 自动派发契约（对标 OMC ultrawork + spawnagent）.
codekanban-cli
Operate CodeKanban workflows, terminal sessions, and web sessions through the installable codekanban-cli command. Use when the user wants to create, inspect, control, watch, or continue CodeKanban AI work from a project path, project ID, or project name without relying on repository-local helper scripts. Prefer…
triage
Work-unit triage for GitHub issues. Groups raw issues, fuses each group with the AGENTS.md northstar, and externalizes each routed unit to a substrate record a collaborator session is pointed at.