What is ticket-complete?

A command for closing a ticket while recording the completed work, lessons learned, and useful discoveries in shared agent memory.

Use it to mark tickets complete, save troubleshooting results, document lessons, share findings, and update dependent work.

It prevents completion details from being lost and helps coordinate related tickets and agents after work is finished.

How lancejames221b/agent-hivemind configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to lancejames221b/agent-hivemind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/lancejames221b/agent-hivemind/master/.claude/commands/ticket-complete.md

Clone the repo

git clone --depth 1 https://github.com/lancejames221b/agent-hivemind

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-complete/github.svg)](https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-complete)

Your own site

<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-complete"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-complete/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-complete"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-complete.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,106 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00011	$0.01106
Opus 5.5	$0.00004	$0.00442
Sonnet 5.5	$0.00002	$0.00221
Haiku 4.5	$0.00001	$0.00111

Measured 2mo ago against content hash 4b9b4198234e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ticket-complete 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 2mo 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.

.claude/commands/ticket-complete.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ticket-complete - Finish Ticket Work with Hooks

Purpose

Complete ticket work with automatic post-work synchronization hooks that store results, document lessons learned, and share discoveries with the hAIveMind collective.

When to Use

Finish Ticket Work: Mark ticket as completed
Knowledge Capture: Store comprehensive results and lessons
Discovery Sharing: Broadcast important findings to other agents
Project Coordination: Update dependent work and relationships

Syntax

ticket-complete <ticket_id> [options] --summary "Work completed summary"

Features

Automatic Post-Work Hooks

When you complete a ticket, the system automatically:

Updates ticket status with detailed completion notes
Stores comprehensive results in hAIveMind memory
Documents lessons learned and troubleshooting solutions
Shares important discoveries with other agents
Coordinates with dependent tickets and agents

Knowledge Preservation

Captures detailed work results and outcomes
Documents troubleshooting steps and solutions
Records lessons learned for future work
Links completion to related memories and tickets

Network Coordination

Broadcasts discoveries to hAIveMind collective
Updates dependent work and blocking relationships
Triggers sync with network-wide knowledge distribution
Notifies coordinating agents of completion

Real-World Examples

Complete Web Testing Ticket

ticket-complete WEBTESTS-1 --summary "Login form validation implemented" --lessons "Email regex validation tricky - use /^[^\s@]+@[^\s@]+\.[^\s@]+$/" --discovery "Found Chrome autofill conflicts with validation"

Automatic Actions:

Updates WEBTESTS-1 status to done
Stores validation implementation details
Documents regex solution for future use
Broadcasts Chrome autofill discovery to team
Coordinates with dependent UI tickets

Complete API Development

ticket-complete API-DEV-5 --summary "Search endpoint implemented" --results "Added pagination, filtering, and sorting" --troubleshooting "Fixed Elasticsearch timeout issues by adding connection pooling"

Automatic Actions:

Marks API development ticket complete
Stores endpoint implementation details
Documents pagination/filtering approach
Records Elasticsearch timeout solution
Shares connection pooling discovery

Read the full file on GitHub · 150 lines

Changes

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.

2mo ago First seen · 150 lines · 11 tokens per session scan A 4b9b4198234e

Subscribe to this mod's changes

ticket-complete is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 1,106 once invoked, about $0.0000 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.

Memory and context Project management

ticket-complete next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ticket-completelancejames221b/agent-hivemind	Command	7	3mo ago	MIT	A	11	Claude Code
minutes-ideassilverstein/minutes	Command	1.6k	yesterday	MIT	A	48	Claude Code, OpenCode
learnReflexioAI/claude-smart	Command	791	3d ago	Apache-2.0	A	14	Claude Code
memory-storeverygoodplugins/mcp-automem	Command	66	yesterday	MIT	A	10	Claude Code
analyze-contextRohiRIK/OpenLtm	Command	29	8d ago	MIT	A	39	Claude Code
cc-memoryTheLobbi/claude	Command	21	7d ago	MIT	A	0	Claude Code
lians-recallLians-ai/Lians	Command	17	5d ago	Apache-2.0	A	19	Claude Code

agent-hivemind: Command for Claude Code