Borrowing it
Nothing to install: this file belongs to DIGI-UW/OpenELIS-Global-2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DIGI-UW/OpenELIS-Global-2/develop/.specify/oe/commands/finish-ticket.mdgit clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2Wrote 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/commands/digi-uw/openelis-global-2/finish-ticket)<a href="https://agentmods.dev/commands/digi-uw/openelis-global-2/finish-ticket"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/finish-ticket/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/commands/digi-uw/openelis-global-2/finish-ticket"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/finish-ticket.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.00000 | $0.01513 |
| Opus 5 | $0.00000 | $0.00757 |
| Sonnet 5 | $0.00000 | $0.00303 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
finish-ticket 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 10d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finish Ticket
Final polish, audit, and validation before marking a ticket ready for review.
Chains existing commands (/audit-branch, formatting, tests) and syncs Jira
status to "In Review."
This is the exit gate of the development cycle — run it when you believe your work is complete and you want a thorough check before requesting review.
User Input
$ARGUMENTS
Flags:
/finish-ticket→ Full audit + format + test + Jira sync + PR ready/finish-ticket --quick→ Format + compile only (skip audit and tests)/finish-ticket --no-jira→ Skip Jira status transition/finish-ticket --no-pr→ Skip PR readiness marking/finish-ticket --deep→ Pass--deepto audit-branch (Tier 3 semantic)/finish-ticket OGC-337→ Explicit Jira key (otherwise auto-detected from branch name)
Atlassian Config
- Cloud ID:
57b4e32d-23d4-4a71-8985-82ac0274d145 - Site:
uwdigi.atlassian.net
Workflow
Step 1: Preflight
Gather context (all parallel):
git branch --show-current # Branch name
git status --porcelain # Uncommitted changes
gh pr view --json number,title,baseRefName,url,isDraft # PR info
- Extract Jira key from branch name (pattern:
<type>/<KEY>-<slug>) or from the$ARGUMENTS - If uncommitted changes exist, warn and ask: commit first or continue?
- If no PR exists, warn but continue (user may want to create one after)
Report:
Branch: feat/OGC-337-implement-generic-astm-plugin-v1
PR: #42 (draft) → develop
Jira: OGC-337
Status: 2 uncommitted files (warn)
Step 2: Format (mandatory)
Run formatting per CLAUDE.md rules — this is non-negotiable before any audit.
Backend (if Java files changed in branch):
mvn spotless:apply
Frontend (if JS/JSX/TS/TSX files changed in branch):
cd frontend && npm run format && cd ..
Check if formatting produced changes:
git diff --stat
If formatting changed files, stage and commit them with message:
style: apply formatting (spotless + prettier)
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.
- 10d ago First seen · 213 lines · 0 tokens per session scan A 35010f83aa07
finish-ticket is a command published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (252 stars, last pushed today), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 1,513 tokens. 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-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.