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.
git 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/hv-list-tickets)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-list-tickets"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-list-tickets/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.
<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-list-tickets"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-list-tickets.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00797 |
| Opus 5.5 | $0.00000 | $0.00319 |
| Sonnet 5.5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
hv-list-tickets 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhanced Ticket Listing Command
Description
List tickets with advanced filtering, status breakdown, and comprehensive ticket details.
Usage
# List all tickets in project
list_tickets project_id="<project_id>"
# Filter by status
list_tickets project_id="<project_id>" status="in_progress"
# Filter by priority and assignee
list_tickets project_id="<project_id>" priority="high" assignee="<agent_id>"
# Filter by type and limit results
list_tickets project_id="<project_id>" ticket_type="bug" limit=10
# Multiple filters combined
list_tickets project_id="<project_id>" status="in_progress" priority="critical" ticket_type="bug" limit=5
Parameters
- project_id: Project ID from Vibe Kanban (required)
- status: Filter by status - new/in_progress/review/done/blocked/cancelled (optional)
- priority: Filter by priority - low/medium/high/critical/emergency (optional)
- assignee: Filter by assignee agent ID (optional)
- ticket_type: Filter by type - bug/feature/task/epic/story/incident/request (optional)
- limit: Maximum tickets to return (default: 20, max: 100)
Status Values
- new: Newly created tickets
- in_progress: Currently being worked on
- review: Under review/testing
- done: Completed tickets
- blocked: Blocked tickets waiting on dependencies
- cancelled: Cancelled/won't fix tickets
Priority Values
- low: 🟢 Low priority
- medium: 🟡 Medium priority (default)
- high: 🟠 High priority
- critical: 🔴 Critical priority
- emergency: 🚨 Emergency priority
Output Format
🎫 Found 15 tickets
Filters: {'status': 'in_progress', 'priority': 'high', 'limit': 20}
📊 Status Breakdown:
in_progress: 15
📋 Ticket List:
#1001 🔴 Fix critical authentication bug
Status: in_progress | Type: bug | Assignee: security-dev
#1002 🟠 Implement user dashboard
Status: in_progress | Type: feature | Assignee: frontend-dev
#1003 🚨 Database connection pool exhaustion
Status: in_progress | Type: incident | Assignee: backend-dev
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 · 111 lines · 0 tokens per session scan A a5d079ef29b2
hv-list-tickets is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 797 tokens. 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.
hv-list-tickets compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| hv-list-ticketslancejames221b/agent-hivemind | Command | 7 | 3mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |