Borrowing it
Nothing to install: this file belongs to VelimirMueller/vlm-code-context-mcp. 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/VelimirMueller/vlm-code-context-mcp/main/.claude/commands/ticket.mdgit clone --depth 1 https://github.com/VelimirMueller/vlm-code-context-mcpWrote 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/velimirmueller/vlm-code-context-mcp/ticket)<a href="https://agentmods.dev/commands/velimirmueller/vlm-code-context-mcp/ticket"><img src="https://agentmods.dev/badge/commands/velimirmueller/vlm-code-context-mcp/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/velimirmueller/vlm-code-context-mcp/ticket"><img src="https://agentmods.dev/badge/commands/velimirmueller/vlm-code-context-mcp/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.00666 |
| Opus 5.5 | $0.00000 | $0.00266 |
| Sonnet 5.5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ticket — Ticket Management
Move tickets through their lifecycle using MCP tools.
Step 0 — Load Context (2 calls)
get_resume_state() # project state + active sprint
get_sprint_playbook() # current phase, gates, next actions
Deferred — use load_phase_context() when needed
| Action | Call |
|---|---|
| View/work on ticket | load_phase_context({ phase: "implementation", sprint_id, ticket_id }) |
| Reassign ticket | list_agents() |
View a ticket
Load full ticket context before acting:
get_ticket({ ticket_id: <id> }) # full details, subtasks, bugs
search_files({ query: "<ticket keywords>" }) # find related code
get_file_context({ path: "<relevant file>", include_changes: false }) # deps only, skip diff history
Before reading any source file with the Read tool, check the code context DB first:
search_files()— find the right file pathget_file_context({ include_changes: false })— deps and exports, skip change history- Only then use Read to see actual content
Move a ticket
update_ticket({ ticket_id: <id>, status: "IN_PROGRESS" })
update_ticket({ ticket_id: <id>, status: "DONE", qa_verified: true, verified_by: "qa" })
update_ticket({ ticket_id: <id>, status: "BLOCKED" })
update_ticket({ ticket_id: <id>, status: "NOT_DONE" })
Reassign a ticket
Check agent workload first:
list_agents() # see who has capacity
load_phase_context({ phase: "retro" }) # includes mood data for workload assessment
Then:
update_ticket({ ticket_id: <id>, assigned_to: "<agent role>" })
Link ticket to epic / milestone
link_ticket_to_epic({ ticket_id: <id>, epic_id: <id> })
link_ticket_to_milestone({ ticket_id: <id>, milestone_id: <id> })
List all tickets in a sprint
get_sprint({ sprint_id: <id> })
Log a bug against a ticket
log_bug({ sprint_id: <id>, ticket_id: <id>, severity: "HIGH", description: "...", expected: "...", actual: "..." })
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 · 92 lines · 0 tokens per session scan A d908a7b96ea8
ticket is a command published in the GitHub repository VelimirMueller/vlm-code-context-mcp (5 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 666 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-31.
Other commands, from other repositories
backlog-from-demo
Turn a recorded product demo into a prioritized backlog with timestamped evidence.
onplana-connect
Sign in to the Onplana MCP server, then verify it works.
staff-event
Build a complete event staffing plan (configured-market match, W-2 rates, tier-based lead time, compliance) and prepare a buyer-submitted quote form.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.