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.
/plugin marketplace add keefar/ticket-flownpx agentmods add plugins/keefar/ticket-flow/marketplacegit clone --depth 1 https://github.com/keefar/ticket-flowGrade A, and why
ticket-flow 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.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "ticket-flow",
"description": "Kanban- or beads-backed git-worktree ticket workflow plugin for Claude Code.",
"owner": { "name": "Christoph Schmid" },
"plugins": [
{
"name": "ticket-flow",
"description": "Kanban- or beads-backed ticket workflow for Claude Code: /spec → /pickup → /implement → /finish, orchestrated by /flow (--local, --parallel, --spawn), each ticket in its own git worktree.",
"source": "./"
}
]
}
What ships with it
1 file beside marketplace.json 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 · 14 lines scan A 4278f8a0bdc3
ticket-flow is a plugin published in the GitHub repository keefar/ticket-flow (4 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
flux
Plugin marketplace listing 1 plugin: flux.
flux
Generate epics and tasks in Flux from project requirements. Ship with less chaos.
cadence
讨论驱动的通用项目工作流插件 — 通过记 / 整 / 查三阶段协议自动落地决定、约束、待决问题和下一步,支持长 session handoff 与跨 session resume(Claude Code 与 OpenCode 均 first-class,Codex 兼容层)。.
fizzy
Operate a self-hosted Fizzy kanban board via fizzy-cli. Use when creating cards or migrating Jira issues to Fizzy.
trello-cli-marketplace
Plugin marketplace listing 1 plugin: trello-cli.
kelvia
The Kelvia plugin for Claude Code: a task board your agent runs, and you can audit.