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 skills add keefar/ticket-flow --skill pushgit 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/push)<a href="https://agentmods.dev/skills/keefar/ticket-flow/push"><img src="https://agentmods.dev/badge/skills/keefar/ticket-flow/push/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/keefar/ticket-flow/push"><img src="https://agentmods.dev/badge/skills/keefar/ticket-flow/push.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00069 | $0.00479 |
| Opus 5.5 | $0.00028 | $0.00192 |
| Sonnet 5.5 | $0.00014 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
push 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 1mo 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
/ticket-flow:push — Push merged commits to origin
Args: none.
Why this exists
/ticket-flow:finish (Phase 3) merges the worktree branch into main but deliberately does not run git push — and /ticket-flow:flow --parallel likewise leaves its merges local. So after a flow chain, main carries commits that are not yet on the remote.
/ticket-flow:push is the one explicit "upload now" step. Keeping push separate and explicit means auth/network failures (gh login, 2FA, keychain, a diverged remote) surface here, in the session you are watching — not silently somewhere else.
Steps
REPO="$(git rev-parse --show-toplevel)" && cd "$REPO"
git fetch origin --quiet 2>/dev/null || true
git push origin main
- Success → report
✓ pushed main → originand the commit range that went up. - Failure → surface the raw
git pusherror, do not retry automatically:- non-fast-forward (someone pushed to origin in the meantime) →
git pull --rebase origin main, then re-run/ticket-flow:push. - auth / 401 →
gh auth login(or fix the keychain), then re-run. - connection error → re-run when back online.
- non-fast-forward (someone pushed to origin in the meantime) →
What it doesn't do
- Force-push (never).
- Push branches other than
main— the merge target of/ticket-flow:finish. - Repo creation for a first-time publish — that is
/ticket-flow:publish. - Auto-retry on transient errors — you decide.
Related
/ticket-flow:publish— first-time publish of a new repo (gh repo create+ initial push)
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.
- 1mo ago First seen · 41 lines · 69 tokens per session scan A 59692c0bdce8
push is a skill published in the GitHub repository keefar/ticket-flow (4 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 479 once invoked, about $0.0003 per session on Opus 5.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
flow-next-land
Resolve feedback and CI for one named pull request, then merge when authorized and ready. Emits LANDVERDICT. Use when asked to land a pull request.
flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
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.
worktree-contributor
Use when starting a work window for multi-agent collaboration - activates contributor role that silently enforces worktree isolation, branch protection, and cross-branch coordination throughout the session.
Git Worktree Design
Planning guidance for Git worktrees. A worktree is a separate working folder linked to the same Git repository, so different branches can be worked on at the same time.
Git PR Description
A pull request, or PR, is a request to merge changes from one Git branch into another. This skill creates the PR title and description from the differences between the current and target branches.