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/publishnpx skills add keefar/ticket-flow --skill publishgit 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/publish)<a href="https://agentmods.dev/skills/keefar/ticket-flow/publish"><img src="https://agentmods.dev/badge/skills/keefar/ticket-flow/publish.svg" alt="Measured on agentmods" 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 | $0.00144 | $0.02390 |
| Opus 5 | $0.00072 | $0.01195 |
| Sonnet 5 | $0.00029 | $0.00478 |
| Haiku 4.5 | $0.00014 | $0.00239 |
Grade A, and why
publish scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w '%{http_code}\n' https://github.com/<owner>/<name>/commit/<sha-of-an-archived-commit> How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ticket-flow:publish — publication state of this repository
One command for everything that moves a repository toward the public — inspecting where it stands, checking what publication would expose, performing the transition, and the first-time creation of the remote. (Formerly two skills, publish and visibility; merged because they answer one question: who can see this repo, and what exactly would they see?)
Why this is its own, deliberately manual step
Making a repository public exposes its entire history, not its current state. And it is one-way in a stronger sense than most irreversible operations:
- Forks made while it was public stay public and are detached from the original.
- Commits stay reachable through the fork network by SHA even after a fork is deleted.
- The moment of publication is recorded in public event archives; the moment of retraction is not recorded at all.
- Measured time from exposure to first access on leaked credentials: seconds to minutes.
- GitHub offers no visibility-based remedy — only revocation and rotation.
So "we can set it back to private" is not a rollback. Everything here runs before. This skill is explicitly user-invoked (disable-model-invocation), and it is never run from a dispatched subagent: auth prompts (gh auth login, 2FA) and remote-conflict errors must be visible in the main session (spec docs/specs/5-push-from-main-session.md, AC C).
Arguments
| Form | Does |
|---|---|
/ticket-flow:publish |
Report the current state and what governs it. Changes nothing. |
/ticket-flow:publish check |
Run the preflight and report findings. Changes nothing. |
/ticket-flow:publish local|private |
Record the state (no publication involved). |
/ticket-flow:publish public |
The guarded transition of an existing repo. Preflight → findings → explicit consent → transition. |
/ticket-flow:publish <owner>/<name> <public|private|internal> |
First-time publish: no origin yet — create the GitHub repo AND push the initial state, atomic via gh repo create --push. A public first-time publish runs the full preflight + consent path first. |
What ships with it
2 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.
- 4d ago First seen · 190 lines · 144 tokens per session scan A 48795a2e1b6f
publish is a skill published in the GitHub repository keefar/ticket-flow (4 stars, last pushed 9d ago), licensed MIT. It adds 144 tokens to every session and 2,390 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-interview
In-depth Q&A to refine a spec, task, or spec file before building. Use when asked to flesh out, refine, or interrogate requirements.
flow-next-audit
Audit .flow/memory/ entries against current code and keep, update, consolidate, replace, delete, or harden each. Use when asked to audit memory or graduate a recurring lesson into a gate.
flow-next-capture
Synthesize the current conversation into a flow-next spec with read-back gating. Use when asked to capture this as a spec.
flow-next-drive
Drive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a non-CDP webview) reached via the Cua Driver / Computer Use. Detects the surface, picks the best available driver, degrades gracefully. Use to…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-make-pr
Open a PR with a cognitive-aid body rendered from flow-next spec state via gh. Use whenever asked to make or open a PR in a flow-next repo.