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-assigngit 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-assign)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-assign"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-assign.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.1 | $0.00014 | $0.01581 |
| Opus 5 | $0.00007 | $0.00790 |
| Sonnet 5 | $0.00003 | $0.00316 |
| Haiku 4.5 | $0.00001 | $0.00158 |
Grade A, and why
ticket-assign 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-assign - Intelligent Ticket Assignment
Purpose
Assign tickets to hAIveMind agents with automatic capability matching, workload balancing, and agent coordination through the collective intelligence network.
When to Use
- Task Delegation: Assign specific tickets to appropriate agents
- Workload Balancing: Distribute work across available agents
- Capability Matching: Find agents with required skills for tickets
- Agent Coordination: Enable cross-agent collaboration on complex work
- Auto-Assignment: Let hAIveMind choose the best agent automatically
Syntax
ticket-assign <ticket_id> [agent_id] [options]
Assignment Methods
Specific Agent Assignment
ticket-assign WEBTESTS-1 frontend-specialist
ticket-assign API-DEV-5 backend-agent --priority high
Auto-Assignment by Capabilities
ticket-assign WEBTESTS-1 --auto --skills "frontend,ui,testing"
ticket-assign INFRA-3 --auto --capabilities "infrastructure,docker,monitoring"
Best Available Agent
ticket-assign API-DEV-5 --best-available
ticket-assign WEBTESTS-2 --best-available --exclude overloaded-agents
Team Assignment
ticket-assign COMPLEX-1 --team "frontend-agent,backend-agent" --collaboration
Agent Discovery Features
Capability Matching
The system automatically:
- Analyzes ticket requirements and complexity
- Matches required skills to agent capabilities
- Considers agent specializations and experience
- Reviews agent performance on similar tickets
Workload Balancing
- Checks current agent workload and capacity
- Considers ticket priorities and deadlines
- Balances work distribution across agents
- Avoids overloading high-performing agents
Agent Coordination
- Links related tickets for collaboration
- Sets up cross-agent dependencies
- Enables knowledge sharing between agents
- Coordinates handoffs and reviews
Real-World Examples
Frontend Work Assignment
ticket-assign WEBTESTS-1 --auto --skills "react,css,testing" --description "Login form needs responsive design and validation"
Automatic Matching:
- Finds agents with React and CSS expertise
- Prioritizes agents with testing experience
- Considers UI/UX specialization
- Balances current frontend workload
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 · 14 tokens per session scan A bf6867ea215e
ticket-assign 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,581 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.