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-my-tickets)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-my-tickets"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-my-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-my-tickets"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-my-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.00934 |
| Opus 5 | $0.00000 | $0.00467 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
hv-my-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 10d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
My Tickets Dashboard Command
Description
Get personalized ticket dashboard showing assigned work, workload summary, and priority breakdown.
Usage
# Get all your tickets
get_my_tickets project_id="<project_id>" assignee="<your_agent_id>"
# Filter by status
get_my_tickets project_id="<project_id>" assignee="<your_agent_id>" status="in_progress"
# Check specific user's tickets
get_my_tickets project_id="<project_id>" assignee="frontend-dev" status="review"
Parameters
- project_id: Project ID from Vibe Kanban (required)
- assignee: Agent ID to get tickets for (required)
- status: Optional status filter - new/in_progress/review/done/blocked/cancelled (optional)
Output Format
👤 frontend-dev's Tickets (8 total)
⏱️ Total Estimated Work: 32h
🏃 In Progress: 3
🚨 High Priority: 2
📋 IN_PROGRESS (3)
#1001 🔴 Fix critical authentication bug (4h)
#1005 🟡 Update user profile page (6h)
#1008 🟠 Implement dark mode toggle (8h)
📋 REVIEW (2)
#1003 🟡 Add form validation messages (3h)
#1007 🟢 Update footer links (1h)
📋 NEW (3)
#1010 🟠 Mobile responsive navigation (8h)
#1012 🟡 Fix CSS layout issues (2h)
#1015 🟢 Update documentation (0h)
Dashboard Features
- ✅ Workload Summary: Total estimated hours across all tickets
- ✅ Status Breakdown: Tickets organized by current status
- ✅ Priority Indicators: Visual priority markers (🚨🔴🟠🟡🟢)
- ✅ Time Estimates: Hours estimated for each ticket
- ✅ Active Work Count: Number of in-progress tickets
- ✅ High Priority Alert: Count of urgent items
- ✅ Personal Focus: Only assigned tickets
Priority Visual Indicators
- 🚨 Emergency: Immediate attention required
- 🔴 Critical: Business-critical issues
- 🟠 High: Important work items
- 🟡 Medium: Standard priority (most common)
- 🟢 Low: Can be deferred if needed
Workload Insights
- Total Estimated: Sum of all time estimates
- In Progress Count: Currently active work
- High Priority Count: Urgent items needing attention
- Status Distribution: Work organized by workflow stage
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.
- 10d ago First seen · 119 lines · 0 tokens per session scan A c17c7cd7300d
hv-my-tickets is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 934 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.
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.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.