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 commands/lancejames221b/agent-hivemind/ticket-completegit clone --depth 1 https://github.com/lancejames221b/agent-hivemindWrote 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/lancejames221b/agent-hivemind/ticket-complete)<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="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.00011 | $0.01106 |
| Opus 5 | $0.00005 | $0.00553 |
| Sonnet 5 | $0.00002 | $0.00221 |
| Haiku 4.5 | $0.00001 | $0.00111 |
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 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.
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 — 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
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 · 150 lines · 11 tokens per session scan A 4b9b4198234e
ticket-complete is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,106 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
checkpoint
Export, refresh, verify, or import a comprehensive cross-topic Project Knowledge Checkpoint for a repository, with privacy checks.
finish-work
Command "finish-work" from DunCanYounG-1/auto-embedded, covering 1. 机械门禁（先跑，不通过不许进 review 结论）, 2. review 三层（缺一不可）, 3. 学习回流（promote，知识复利的关键）, 4. 会话记忆（journal，跨会话续上下文） and 5. 归档.
adr
Create an Architecture Decision Record in memory-bank BACKLOG.
lavra-checkpoint
Save session progress by filing beads, capturing knowledge, and syncing state.
project-status
Show current project status or initialize a new project.
gaai-status
Show backlog, memory state & delivery readiness.