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/recentgit 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.00013 | $0.03670 |
| Opus 5 | $0.00006 | $0.01835 |
| Sonnet 5 | $0.00003 | $0.00734 |
| Haiku 4.5 | $0.00001 | $0.00367 |
Grade A, and why
recent 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
recent - Command History & Pattern Analysis
Purpose
Intelligent command history system that shows your recently used hAIveMind commands with success rates, execution times, and pattern analysis to help optimize your workflow and identify improvement opportunities.
When to Use
- Performance Analysis: Review command success rates and execution times
- Workflow Optimization: Identify patterns in your command usage for efficiency improvements
- Troubleshooting: Analyze recent failures to identify recurring issues
- Learning: Understand your usage patterns and discover optimization opportunities
- Audit Trail: Review recent actions for compliance or debugging purposes
- Pattern Recognition: Discover successful command sequences for future use
Syntax
recent [limit]
Parameters
- limit (optional): Number of recent commands to display (default: 10, max: 50)
- Examples:
recent 5,recent 20,recent 50
- Examples:
Intelligent Analysis Features
Usage Pattern Recognition
- Command Sequences: Identifies common command patterns and their success rates
- Timing Analysis: Analyzes time between commands to identify workflow efficiency
- Success Correlation: Shows which command combinations lead to best outcomes
- Context Awareness: Correlates command usage with project types and situations
- Trend Analysis: Identifies changes in usage patterns over time
Performance Insights
- Execution Time Tracking: Shows how long each command took to complete
- Success Rate Analysis: Tracks which commands succeed most often
- Error Pattern Detection: Identifies recurring failure patterns
- Efficiency Metrics: Calculates workflow efficiency and suggests improvements
- Comparative Analysis: Compares your patterns with collective best practices
Real-World Examples
Basic Recent Command History
recent
Result: Last 10 commands with timestamps, success status, execution times, and context
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 · 373 lines · 13 tokens per session scan A de2eaf590e37
recent is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 3,670 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
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.