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/hv-create-ticketgit 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-create-ticket)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-create-ticket"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-create-ticket.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.00000 | $0.00805 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
hv-create-ticket 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhanced Ticket Creation Command
Description
Create comprehensive tickets with metadata, priority, assignment, and hAIveMind integration.
Usage
# Basic ticket creation
create_ticket project_id="<project_id>" title="<title>" description="<description>"
# Full ticket with all metadata
create_ticket project_id="<project_id>" title="<title>" description="<description>" ticket_type="bug" priority="high" assignee="<agent_id>" labels="[\"label1\", \"label2\"]" due_date="2024-12-31T23:59:59" time_estimate=8 reporter="<user_id>"
# Epic creation
create_ticket project_id="<project_id>" title="User Authentication Epic" description="Complete user authentication system" ticket_type="epic" priority="high" time_estimate=40
# Bug report with assignee
create_ticket project_id="<project_id>" title="Login form validation error" description="Email validation not working on login form" ticket_type="bug" priority="critical" assignee="frontend-dev" labels="[\"ui\", \"validation\"]"
# Feature request
create_ticket project_id="<project_id>" title="Add dark mode theme" description="Users request dark mode for better usability" ticket_type="feature" priority="medium" labels="[\"ui\", \"enhancement\"]" time_estimate=12
Parameters
- project_id: Project ID from Vibe Kanban (required)
- title: Ticket title (required)
- description: Detailed description (optional)
- ticket_type: Type - bug/feature/task/epic/story/incident/request (default: task)
- priority: Priority - low/medium/high/critical/emergency (default: medium)
- assignee: Agent ID to assign ticket to (optional)
- labels: JSON array of labels ["label1", "label2"] (optional)
- due_date: Due date in ISO format (optional)
- time_estimate: Estimated hours as integer (optional)
- parent_ticket: Parent ticket ID for subtasks (optional)
- reporter: Reporter/creator ID (default: system)
Features
- ✅ Comprehensive metadata support
- ✅ Priority and type classification
- ✅ Time estimation and tracking
- ✅ Label categorization
- ✅ Agent assignment
- ✅ Due date management
- ✅ Parent-child relationships
- ✅ hAIveMind memory integration
- ✅ Automatic ticket numbering
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.
- 6d ago First seen · 65 lines · 0 tokens per session scan A b3b7ab411982
hv-create-ticket 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 805 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.