A one-time setup command for a ticket-flow project, including its Beads task tracker, specification folders, and Git worktree settings. It can also migrate an existing KANBAN.md board into Beads.

Use it when adding ticket-flow to a project, passing setup options to Beads, or migrating an older board-based setup.

It prepares a repository for the ticket workflow and establishes the files and directories needed to manage and implement tickets.

init — Skill by keefar

Install

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.

agentmods

npx agentmods add skills/keefar/ticket-flow/init

Any agent

npx skills add keefar/ticket-flow --skill init

Clone the repo

git clone --depth 1 https://github.com/keefar/ticket-flow

Made for: Claude Code, Codex.

Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,980 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00108	$0.04980
Opus 5	$0.00054	$0.02490
Sonnet 5	$0.00022	$0.00996
Haiku 4.5	$0.00011	$0.00498

Measured yesterday against content hash 34d420cd8999, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

init 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 yesterday.

The scan reads SKILL.md. This mod also ships 10 executable files (install-routing-rule.sh, install-worktree-include.sh, set-worktree-baseref.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/init/SKILL.md · 294 lines

How it starts

The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/ticket-flow:init — Scaffold ticket-flow project files

Args:

(none) — scaffold the project (beads is the only backend). --mode=beads / --beads are accepted as no-op legacy spellings; --mode=kanban is refused with a pointer to the removed mode.
Pass-throughs (forwarded to bd init): --skip-agents, --stealth, --non-interactive, --prefix, --role, etc.

What it does

Sets up a project for ticket-flow on beads — the only backend since the mode=kanban removal (the dual-mode code is preserved at refs/archive/mode-kanban). No .ticket-flow flag is written anymore; a leftover mode=kanban flag marks an unmigrated project and this skill is the migration path.

Scaffolding:

docs/specs/SPEC-TEMPLATE.md — template that /ticket-flow:spec copies from
docs/superpowers/plans/.gitkeep — directory for implementation plans (used by superpowers:writing-plans)
.claude/worktrees/ — directory where /ticket-flow:pickup creates branch worktrees
.worktreeinclude — gitignored local config (.env, *.local, …) that must follow a ticket into its worktree; seeded from what the repo actually has, skipped when there is nothing (via skills/init/install-worktree-include.sh)
.claude/settings.json → worktree.symlinkDirectories — dependency directories (node_modules, vendor, …) linked back to the main checkout instead of reinstalled per worktree; build outputs deliberately excluded (via skills/init/set-worktree-symlinks.sh)
.claude/rules/ticket-flow-routing.md — the Ticket-Flow Routing rule (via skills/init/install-routing-rule.sh) so planning/ideation prompts route through tf instead of superpowers:brainstorming or superpowers:writing-plans. A rule without a paths: frontmatter key loads at launch with the same priority as .claude/CLAUDE.md (memory docs) — same effect, without writing into the consumer project's own CLAUDE.md. Idempotent (the file's existence is the guard); a routing block left in CLAUDE.md by an older init is removed.

Read the full file on GitHub · 294 lines

Files

What ships with it

12 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.

Changes

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.

yesterday First seen · 294 lines · 108 tokens per session scan A 34d420cd8999

Subscribe to this mod's changes

init is a skill published in the GitHub repository keefar/ticket-flow (4 stars, last pushed 6d ago), licensed MIT. It adds 108 tokens to every session and 4,980 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.

Git and workflow Memory and context Project management claude-code git-worktree kanban plugin workflow

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…

rookedsysc/kanvibe · 112 tokens

council-router

Route code reviews to appropriate council members. Use when reviewing PRs, architecture decisions, or significant code changes that need expert perspective.

automagik-dev/forge · 31 tokens

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…

fy0/CodeKanban · 102 tokens

init