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/quantulabs/hivemind/hivestatsgit clone --depth 1 https://github.com/QuantuLabs/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/quantulabs/hivemind/hivestats)<a href="https://agentmods.dev/commands/quantulabs/hivemind/hivestats"><img src="https://agentmods.dev/badge/commands/quantulabs/hivemind/hivestats.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 | $0.00000 | $0.00361 |
| Opus 5 | $0.00000 | $0.00180 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
hivestats 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 3d 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.
What it actually says
Hivemind Usage Statistics
Display token usage and cost statistics for Hivemind API calls.
Instructions
Use the mcp__hivemind__check_stats tool to display usage statistics.
Present the statistics in a clear, formatted way:
-
Session Statistics - Usage since the MCP server started
- Duration
- Total requests, tokens, and cost
- Per-provider breakdown (OpenAI, Anthropic, Google)
-
Monthly Statistics - Cumulative usage for the current month
- Same breakdown as session stats
- Persisted across server restarts
-
Pricing Reference - Current token pricing per provider
Notes
- Token counts are estimates based on content length (~4 chars/token)
- Costs are calculated using current API pricing (January 2026)
- Monthly stats are stored in
~/.config/hivemind/usage.json - Session stats reset when the MCP server restarts
Example Output
## Session Statistics
Duration: 2h 15m
Total Requests: 42
Total Tokens: 125.5K
Total Cost: $0.4521
### OpenAI
Requests: 14
Input: 28.2K tokens
Output: 18.5K tokens
Cost: $0.1523
### Google
Requests: 28
Input: 45.0K tokens
Output: 33.8K tokens
Cost: $0.2998
## Monthly Statistics
Month: 2026-01
Total Requests: 156
Total Tokens: 892.3K
Total Cost: $2.8847
...
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.
- 3d ago First seen · 57 lines · 0 tokens per session scan A c2794cadb043
hivestats is a command published in the GitHub repository QuantuLabs/Hivemind (1 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 361 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.