A command for searching shared records of previous technical work and asking specialist agents for answers. The records can include incidents, deployments, security issues, monitoring, infrastructure, and operating procedures.

Use it to investigate technical problems, look up configuration advice, research incidents, and find procedures or best practices from the shared knowledge base.

It helps you find earlier solutions, decisions, and troubleshooting guidance instead of starting from an empty search or repeating past work.

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/hv-query.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/hv-query/github.svg)](https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-query)

Your own site

<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-query"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-query/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/hv-query"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-query.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 2,411 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.02411
Opus 5.5	$0.00004	$0.00964
Sonnet 5.5	$0.00002	$0.00482
Haiku 4.5	$0.00001	$0.00241

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

Security

Grade A, and why

hv-query 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/hv-query.md · 290 lines

How it starts

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

hv-query - Collective Knowledge Search

Purpose

Search the hAIveMind collective memory and query specialized agents for comprehensive answers combining stored knowledge with real-time expertise.

When to Use

Troubleshooting Issues: Find solutions to problems encountered before
Best Practices: Learn how other agents handle similar situations
Configuration Guidance: Get infrastructure setup recommendations
Incident Research: Find related incidents and their resolutions
Technical Questions: Tap into specialized agent knowledge
Historical Context: Understand past decisions and their outcomes

Syntax

hv-query "question or topic" [category] [options]

Parameters

question (required): Clear, specific question or topic to search
category (optional): Narrow search to specific memory types
- infrastructure: Server configs, network topology, hardware
- incidents: Outage reports, resolutions, post-mortems
- deployments: Release procedures, rollbacks, configurations
- security: Vulnerabilities, patches, compliance, audits
- monitoring: Alerts, metrics, dashboards, thresholds
- runbooks: Procedures, scripts, operational guides
options (optional):
- --agent=name: Query specific agent directly (e.g., --agent=elastic1-specialist)
- --recent=hours: Limit to memories from last N hours (e.g., --recent=24)
- --semantic: Use semantic search only (default: hybrid)
- --exact: Use exact text matching only

Query Intelligence Features

Hybrid Search Strategy

Semantic Search: Finds conceptually related information
Full-Text Search: Locates exact phrases and technical terms
Agent Expertise: Routes questions to specialists
Context Correlation: Links related memories automatically

Agent Expertise Routing

Database Issues → mysql-specialist, mongodb-specialist
Elasticsearch Problems → elastic1-specialist, cluster-manager
Security Questions → security-analyst, auth-specialist
Network Issues → infrastructure-manager, network-specialist
Code Questions → development-team, code-reviewer

Read the full file on GitHub · 290 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 · 290 lines · 0 tokens per session scan A ebe01fb52505

Subscribe to this mod's changes

hv-query 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 2,411 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.

Memory and context

hv-query next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
hv-querylancejames221b/agent-hivemind	Command	7	3mo ago	MIT	A	11	Claude Code
minutes-ideassilverstein/minutes	Command	1.6k	yesterday	MIT	A	48	Claude Code, OpenCode
learnReflexioAI/claude-smart	Command	791	3d ago	Apache-2.0	A	14	Claude Code
memory-storeverygoodplugins/mcp-automem	Command	66	yesterday	MIT	A	10	Claude Code
analyze-contextRohiRIK/OpenLtm	Command	29	8d ago	MIT	A	39	Claude Code
cc-memoryTheLobbi/claude	Command	21	7d ago	MIT	A	0	Claude Code
lians-recallLians-ai/Lians	Command	17	5d ago	Apache-2.0	A	19	Claude Code

agent-hivemind: Command for Claude Code