A command that shows step-by-step workflows for hAIveMind operations, including incident response, maintenance, security audits, deployment, and monitoring.

Use it to look up procedures for handling incidents, maintaining systems, auditing security, deploying or rolling back software, and setting up monitoring.

It helps you find the expected order of commands for multi-step operational work instead of assembling the procedure from memory.

How lancejames221b/agent-hivemind configures Claude Code

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/workflows.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/workflows/github.svg)](https://agentmods.dev/commands/lancejames221b/agent-hivemind/workflows)

Your own site

<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/workflows"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/workflows/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/workflows"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,702 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.03702
Opus 5.5	$0.00004	$0.01481
Sonnet 5.5	$0.00002	$0.00740
Haiku 4.5	$0.00001	$0.00370

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

Security

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 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/workflows.md · 431 lines

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 procedures
- daily_maintenance - Regular system health and maintenance routines
- security_audit - Comprehensive security assessment workflows
- deployment - Application deployment and rollback procedures
- monitoring_setup - Proactive monitoring and alerting configuration
- knowledge_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

Read the full file on GitHub · 431 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.

2mo ago First seen · 431 lines · 11 tokens per session scan A 52ed931e1ba0

Subscribe to this mod's changes

workflows is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 3,702 once invoked, about $0.0000 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.

Building agents

workflows next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
workflowslancejames221b/agent-hivemind	Command	7	3mo ago	MIT	A	11	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

agent-hivemind: Command for Claude Code