agent-hivemind: Command for Claude Code

.claude/commands/ticket-start.md

ticket-start is a command for Claude Code from lancejames221b/agent-hivemind. It costs 13 tokens per session (801 once invoked), scanned A, original, MIT.

A command for beginning work on a ticket with automatic context and dependency checks. A ticket is a tracked piece of work in a project.

In plain words
What is it for?
Use it to read a ticket's status, search and update shared hAIveMind memory, identify blockers, link dependencies, and record lessons from similar work.
Why use it?
It gathers related information and records the planned work before implementation, so agents start with shared context.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is lancejames221b/agent-hivemind's own configuration. It tells Claude Code how to work on agent-hivemind itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-hivemind configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lancejames221b/agent-hivemind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/lancejames221b/agent-hivemind/master/.claude/commands/ticket-start.md
Clone the repo
git clone --depth 1 https://github.com/lancejames221b/agent-hivemind

Made for: Claude Code.

Wrote 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.

agentmods badge for ticket-start

README.md
[![agentmods](https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-start/github.svg)](https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-start)
Your own site
<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-start"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-start/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.

agentmods 80×15 button for ticket-start

Your own site · 80×15
<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/ticket-start"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/ticket-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 801 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00801
Opus 5.5 $0.00005 $0.00320
Sonnet 5.5 $0.00003 $0.00160
Haiku 4.5 $0.00001 $0.00080

Measured 2mo ago against content hash 2285283b8cfa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ticket-start 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.

.claude/commands/ticket-start.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ticket-start - Begin Ticket Work with Hooks

Purpose

Start work on a ticket with automatic pre-work synchronization hooks that capture context, check related memories, and store work intentions in the hAIveMind collective.

When to Use

  • Begin New Work: Starting any ticket or task
  • Context Capture: Automatically gather related information
  • Memory Integration: Link ticket work to collective knowledge
  • Agent Coordination: Notify other agents of work beginning

Syntax

ticket-start <ticket_id> [project_id] [options]

Features

Automatic Pre-Work Hooks

When you start a ticket, the system automatically:

  1. Reads ticket description and current status
  2. Checks hAIveMind memory for related context
  3. Stores work intention with expected outcomes
  4. Identifies dependencies and blocking issues
  5. Reviews lessons learned from similar work

Memory Integration

  • Searches collective memory for related work
  • Stores work context for other agents
  • Links dependencies and relationships
  • Captures lessons learned from similar tickets

Real-World Examples

Start Web Testing Ticket

ticket-start WEBTESTS-1 memory-mcp-project

Automatic Actions:

  • Reads WEBTESTS-1 ticket details
  • Searches for related web testing memories
  • Stores intention to start web testing work
  • Checks for UI/UX testing dependencies
  • Reviews lessons from previous web testing

Start API Development

ticket-start API-DEV-5 ewitness-project --verbose

Automatic Actions:

  • Captures API development context
  • Links to related API memories
  • Stores development work intention
  • Identifies authentication dependencies
  • Reviews API development best practices

Resume Previous Work

ticket-start INFRA-3 --resume

Automatic Actions:

  • Checks previous work context
  • Reviews any blocking issues resolved
  • Updates work intention
  • Syncs with latest infrastructure state

Expected Output

🚀 Starting Work on Ticket: WEBTESTS-1
🔄 Executing Pre-Work Synchronization Hooks...

✅ Pre-Work Hook Results:
   • pre_work_hook (0.245s)

📋 Ticket Context Captured:
   • Title: "Login form validation testing"
   • Status: todo → inprogress
   • Project: memory-mcp-project

🧠 Memory Integration:
   • Related memories found: 7
   • Dependencies identified: 2
   • Lessons learned retrieved: 3

💾 Work intention stored in hAIveMind collective
🤖 Other agents notified of work beginning

🎯 Ready to begin work! Use ticket-complete when finished.

Read the full file on GitHub · 117 lines

Changes

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.

  1. 2mo ago First seen · 117 lines · 13 tokens per session scan A 2285283b8cfa

Subscribe to this mod's changes

ticket-start is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 801 once invoked, about $0.0001 per session on Opus 5.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.

Related

ticket-start compared with commands from other repositories

ticket-start next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ticket-startlancejames221b/agent-hivemindCommand73mo agoMITA13Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code