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.
git clone --depth 1 https://github.com/airmcp-com/mcp-standardsWrote 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/airmcp-com/mcp-standards/overview)<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/overview"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/overview/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.
<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/overview"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/overview.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00962 |
| Opus 5.5 | $0.00000 | $0.00385 |
| Sonnet 5.5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
overview 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 1mo 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.
This is a copy
100% identical to overview — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Hooks for claude-flow
Purpose
Automatically coordinate, format, and learn from Claude Code operations using hooks with MCP tool integration.
Available Hooks
Pre-Operation Hooks
- pre-edit: Validate and assign agents before file modifications
- pre-bash: Check command safety and resource requirements
- pre-task: Auto-spawn agents for complex tasks
Post-Operation Hooks
- post-edit: Auto-format code, train neural patterns, update memory
- post-bash: Log execution and update metrics
- post-search: Cache results and improve search patterns
MCP Integration Hooks
- mcp-initialized: Persist swarm configuration
- agent-spawned: Update agent roster and memory
- task-orchestrated: Monitor task progress through memory
- neural-trained: Save pattern improvements
Memory Coordination Hooks
- memory-write: Triggered when agents write to coordination memory
- memory-read: Triggered when agents read from coordination memory
- memory-sync: Synchronize memory across swarm agents
Session Hooks
- notify: Custom notifications with swarm status
- session-end: Generate summary and save state
- session-restore: Load previous session state
Configuration
Hooks are configured in .claude/settings.json:
{
"hooks": {
"PreToolUse": [
{
"matcher": "^(Write|Edit|MultiEdit)$",
"hooks": [{
"type": "command",
"command": "npx claude-flow hook pre-edit --file '${tool.params.file_path}' --memory-key 'swarm/editor/current'"
}]
}
],
"PostToolUse": [
{
"matcher": "^(Write|Edit|MultiEdit)$",
"hooks": [{
"type": "command",
"command": "npx claude-flow hook post-edit --file '${tool.params.file_path}' --memory-key 'swarm/editor/complete'"
}]
}
]
}
}
MCP Tool Integration in Hooks
Hooks automatically trigger MCP tools for coordination:
// Pre-task hook spawns agents
npx claude-flow hook pre-task --description "[task]"
// Internally calls:
mcp__claude-flow__agent_spawn { type: "appropriate-agent" }
// Post-edit hook updates memory
npx claude-flow hook post-edit --file "[file]"
// Internally calls:
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm/editor/[file]",
namespace: "coordination",
value: JSON.stringify({ file, changes, timestamp })
}
// Session-end hook persists state
npx claude-flow hook session-end
// Internally calls:
mcp__claude-flow__memory_persist { sessionId: "[session-id]" }
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.
- 1mo ago First seen · 132 lines · 0 tokens per session scan A d2343edebcb3
overview is a command published in the GitHub repository airmcp-com/mcp-standards (3 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 962 tokens. A static security scan graded it A with 0 findings. It is 100% identical to overview, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
learn
A command for recording lessons learned from direct notes, recent errors, or the current work session. It can classify lessons, suggest automations from git history, and manage the saved list.
plan
A command for creating a detailed work plan for a feature, bug fix, refactor, or experiment. It saves the plan in a memory bank, a project folder used to keep planning information.
done
A session-ending command for a project that uses a memory bank, a set of files storing project context and progress. It runs required checks, updates the core memory-bank files and adds a progress note.
setup
Interview me and scaffold my personal chief-of-staff system (context file, memory, task list, daily brief).
start
A session-start command that loads the project's Memory Bank, a set of files containing saved project context and status.