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-startgit 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-start)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-start"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-start.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.00013 | $0.00801 |
| Opus 5 | $0.00006 | $0.00400 |
| Sonnet 5 | $0.00003 | $0.00160 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
ticket-start 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ticket-start - Begin Ticket Work with Hooks
Purpose
Start work on a ticket with automatic pre-work synchronization hooks that capture context, check related memories, and store work intentions in the hAIveMind collective.
When to Use
- Begin New Work: Starting any ticket or task
- Context Capture: Automatically gather related information
- Memory Integration: Link ticket work to collective knowledge
- Agent Coordination: Notify other agents of work beginning
Syntax
ticket-start <ticket_id> [project_id] [options]
Features
Automatic Pre-Work Hooks
When you start a ticket, the system automatically:
- Reads ticket description and current status
- Checks hAIveMind memory for related context
- Stores work intention with expected outcomes
- Identifies dependencies and blocking issues
- Reviews lessons learned from similar work
Memory Integration
- Searches collective memory for related work
- Stores work context for other agents
- Links dependencies and relationships
- Captures lessons learned from similar tickets
Real-World Examples
Start Web Testing Ticket
ticket-start WEBTESTS-1 memory-mcp-project
Automatic Actions:
- Reads WEBTESTS-1 ticket details
- Searches for related web testing memories
- Stores intention to start web testing work
- Checks for UI/UX testing dependencies
- Reviews lessons from previous web testing
Start API Development
ticket-start API-DEV-5 ewitness-project --verbose
Automatic Actions:
- Captures API development context
- Links to related API memories
- Stores development work intention
- Identifies authentication dependencies
- Reviews API development best practices
Resume Previous Work
ticket-start INFRA-3 --resume
Automatic Actions:
- Checks previous work context
- Reviews any blocking issues resolved
- Updates work intention
- Syncs with latest infrastructure state
Expected Output
🚀 Starting Work on Ticket: WEBTESTS-1
🔄 Executing Pre-Work Synchronization Hooks...
✅ Pre-Work Hook Results:
• pre_work_hook (0.245s)
📋 Ticket Context Captured:
• Title: "Login form validation testing"
• Status: todo → inprogress
• Project: memory-mcp-project
🧠 Memory Integration:
• Related memories found: 7
• Dependencies identified: 2
• Lessons learned retrieved: 3
💾 Work intention stored in hAIveMind collective
🤖 Other agents notified of work beginning
🎯 Ready to begin work! Use ticket-complete when finished.
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 · 117 lines · 13 tokens per session scan A 2285283b8cfa
ticket-start is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 801 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
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.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].