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/workflowsgit clone --depth 1 https://github.com/lancejames221b/agent-hivemindWhat 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 | $0.00011 | $0.03702 |
| Opus 5 | $0.00005 | $0.01851 |
| Sonnet 5 | $0.00002 | $0.00740 |
| Haiku 4.5 | $0.00001 | $0.00370 |
Grade A, and why
workflows 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 2d 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 — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workflows - Command Workflows & Patterns
Purpose
Comprehensive workflow system that provides step-by-step guidance for common operational patterns, showing how hAIveMind commands work together to accomplish complex tasks efficiently and reliably.
When to Use
- Complex Operations: Multi-step procedures requiring coordination across multiple agents
- Incident Response: Structured approach to handling system outages and emergencies
- Daily Operations: Routine maintenance and monitoring workflows
- Security Procedures: Systematic security assessment and response workflows
- Deployment Management: Coordinated deployment and rollback procedures
- Knowledge Transfer: Learning operational best practices from collective experience
Syntax
workflows [workflow_type]
Parameters
- workflow_type (optional): Specific workflow category to display
incident_response- Emergency incident handling proceduresdaily_maintenance- Regular system health and maintenance routinessecurity_audit- Comprehensive security assessment workflowsdeployment- Application deployment and rollback proceduresmonitoring_setup- Proactive monitoring and alerting configurationknowledge_management- Information capture and sharing workflows
Intelligent Workflow Features
Context-Aware Recommendations
- Incident Detection: Automatically suggests incident response workflows during active issues
- Project Type Adaptation: Workflows adapted for Python, Node.js, Rust, Go projects
- Agent Availability: Adjusts workflows based on currently available specialist agents
- Historical Success: Prioritizes workflows with highest success rates
- Time-Sensitive Operations: Highlights urgent workflows during critical situations
Success Metrics and Analytics
- Completion Rates: Shows workflow success percentages based on historical data
- Time Estimates: Realistic time estimates based on actual execution data
- Bottleneck Identification: Identifies common failure points and provides alternatives
- Performance Optimization: Suggests workflow improvements based on collective experience
- Effectiveness Tracking: Monitors which workflows lead to successful outcomes
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.
- 2d ago First seen · 431 lines · 11 tokens per session scan A 52ed931e1ba0
workflows is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 3,702 once invoked, about $0.0001 per session on Opus 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.
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.