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 skills add LuuOW/meridian-mcp --skill orchestrationgit clone --depth 1 https://github.com/LuuOW/meridian-mcpWrote 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/skills/luuow/meridian-mcp/orchestration)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/orchestration"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/orchestration/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/skills/luuow/meridian-mcp/orchestration"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/orchestration.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.00041 | $0.01777 |
| Opus 5 | $0.00020 | $0.00889 |
| Sonnet 5 | $0.00008 | $0.00355 |
| Haiku 4.5 | $0.00004 | $0.00178 |
Grade A, and why
orchestration 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 9d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orchestration
Covers multi-agent system design: how agents start up, maintain memory, delegate tasks, communicate, and coordinate work across sessions.
1) Agent session startup protocol
# Canonical startup sequence (from AGENTS.md)
1. Read SOUL.md — identity, principles, non-negotiables
2. Read USER.md — who you serve, their preferences and goals
3. Read AGENTS.md — this session protocol and available agents
4. Read memory/TODAY.md — what happened today so far
5. Read memory/YYYY-MM-DD.md — yesterday's notes if today's empty
6. Check MEMORY.md index — long-term context (scan, don't deep-read)
7. Read project README — only if the task is project-specific
# Total token budget for startup: < 8,000 tokens
# If startup reads exceed this, summarise before proceeding
2) Memory protocol
# Memory file hierarchy
MEMORY_STRUCTURE = {
"session": "memory/YYYY-MM-DD.md", # daily notes, in-progress context
"index": "MEMORY.md", # persistent long-term index
"entries": "memory/", # individual memory entries
}
# Daily note format
DAILY_NOTE_TEMPLATE = """
# {date}
## Done today
- {completed_task_1}
- {completed_task_2}
## In progress
- {wip_task}: {status_and_next_step}
## Decisions made
- {decision}: {rationale}
## Blockers
- {blocker}: {what_is_needed}
## Tomorrow
- {priority_1}
"""
# Write to memory after significant work (not after every action)
WRITE_THRESHOLD = "significant decision, completed unit of work, or end of session"
3) Task delegation patterns
# Delegation contract: what to hand off and what to expect back
DELEGATION_SPEC = {
"task": str, # precise instruction (verb-first)
"context": str, # minimum context the sub-agent needs
"output": str, # exact format expected back
"timeout": int, # seconds before assuming failure
"fallback": str, # what to do if delegation fails
}
# Example: orchestrator delegates to a specialist
delegate(
to="seo-agent",
task="Analyse SERP for 'keto diet for beginners' and return top-3 citation gaps",
context=f"Domain: ketoandhealthy.com. Existing article: /keto-diet/beginners",
output="JSON: [{source_url, gap_type, suggested_citation}]",
timeout=120,
fallback="Use cached SERP data from last 24h",
)
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.
- 9d ago First seen · 211 lines · 41 tokens per session scan A 3c12242ba947
orchestration is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,777 once invoked, about $0.0002 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 skills, from other repositories
swarmclaw
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
agent-engineering-expert
Build LLM agents that use tools safely: tool design, the agent loop, memory, MCP servers, multi-agent orchestration, sandboxing and prompt-injection defence. Use when the user mentions AI agents, tool use or function calling, MCP or Model Context Protocol, autonomous workflows, multi-agent systems, LangChain or…
swarmvault
Use when working with a SwarmVault knowledge vault (raw/, wiki/, swarmvault.schema.md). Establishes schema-first conventions and prefers graph queries over broad search.
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…