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-listgit 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-list)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-list"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-list.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.00014 | $0.01408 |
| Opus 5 | $0.00007 | $0.00704 |
| Sonnet 5 | $0.00003 | $0.00282 |
| Haiku 4.5 | $0.00001 | $0.00141 |
Grade A, and why
ticket-list 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 5d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ticket-list - hAIveMind Ticket Browser
Purpose
List, filter, and browse tickets across hAIveMind projects with integrated memory context and agent coordination information.
When to Use
- Project Planning: Review all project tickets and status
- Workload Management: See agent assignments and capacity
- Progress Tracking: Monitor ticket completion across projects
- Context Discovery: Find tickets related to current work
- Dependency Analysis: Understand ticket relationships
Syntax
ticket-list [project_id] [options]
Filtering Options
By Project
ticket-list memory-mcp-project
ticket-list ewitness-project --status todo
By Status
ticket-list --status inprogress
ticket-list --status done --limit 20
ticket-list --status todo,inreview
By Agent
ticket-list --agent frontend-specialist
ticket-list --assigned-to lj-agent
ticket-list --unassigned
By Priority
ticket-list --priority high,critical
ticket-list --priority low --status todo
By Tags
ticket-list --tags webtests,ui
ticket-list --tags api,security --status inprogress
By Date Range
ticket-list --created-since 2025-01-20
ticket-list --updated-today
ticket-list --completed-this-week
Memory Integration Features
Related Context
Each ticket shows:
- Related hAIveMind memories count
- Linked lessons learned and solutions
- Connected troubleshooting knowledge
- Associated project context
Agent Coordination
Displays:
- Current agent assignments
- Agent workload and capacity
- Cross-agent dependencies
- Collaboration patterns
Knowledge Discovery
Finds:
- Similar completed work
- Relevant troubleshooting solutions
- Applicable lessons learned
- Connected discoveries
Output Formats
Compact List (Default)
📋 Project: memory-mcp (8 tickets)
🎫 WEBTESTS-1: Login form validation [DONE]
👤 frontend-agent | 🧠 5 memories | ⏰ 2d ago
🎫 WEBTESTS-2: Dashboard UI testing [IN PROGRESS]
👤 ui-specialist | 🧠 3 memories | ⏰ 1h ago
🎫 WEBTESTS-3: API integration tests [TODO]
👤 unassigned | 🧠 7 memories | ⏰ 3d ago
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.
- 5d ago First seen · 206 lines · 0 tokens per session scan A 8ce46344cd64
ticket-list is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,408 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.