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-ticket-metrics)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-ticket-metrics"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-ticket-metrics/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-ticket-metrics"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-ticket-metrics.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.00896 |
| Opus 5 | $0.00000 | $0.00448 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
hv-ticket-metrics 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Metrics and Analytics Command
Description
Get comprehensive ticket metrics, analytics, and performance insights for project management.
Usage
# Get 30-day metrics (default)
get_ticket_metrics project_id="<project_id>"
# Get metrics for specific time period
get_ticket_metrics project_id="<project_id>" days=7
# Get quarterly metrics
get_ticket_metrics project_id="<project_id>" days=90
Parameters
- project_id: Project ID from Vibe Kanban (required)
- days: Time period for metrics calculation (default: 30, max: 365)
Output Format
📊 Ticket Metrics (30 days)
Generated: 2024-08-27T18:00:00Z
📈 Overview:
Total Tickets: 45
Created in Period: 12
Closed in Period: 8
Average Resolution: 18.5h
📊 By Status:
in_progress: 15
review: 8
done: 18
new: 4
🚨 By Priority:
medium: 22
high: 12
critical: 8
low: 3
🎯 By Type:
task: 18
bug: 15
feature: 8
incident: 4
⚠️ Alerts:
Critical Tickets: 8
Overdue Tickets: 3
Metrics Included
Overview Metrics
- Total Tickets: All tickets in the project
- Created in Period: New tickets in specified timeframe
- Closed in Period: Completed tickets in timeframe
- Average Resolution Time: Mean time from creation to completion
Status Distribution
- new: Newly created, not yet started
- in_progress: Currently being worked on
- review: Under review or testing
- done: Completed and closed
- blocked: Waiting on dependencies
- cancelled: Cancelled or won't fix
Priority Analysis
- low 🟢: Low impact, can be deferred
- medium 🟡: Standard priority work
- high 🟠: Important, should be prioritized
- critical 🔴: Business-critical issues
- emergency 🚨: Immediate attention required
Type Breakdown
- task: General work items
- bug: Defects and issues
- feature: New functionality
- epic: Large initiatives
- story: User stories
- incident: Production issues
- request: User requests
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 · 135 lines · 0 tokens per session scan A bb1dd90554ed
hv-ticket-metrics 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 896 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.