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 metagit-ai/metagit-cli --skill metagit-agent-coordinationgit clone --depth 1 https://github.com/metagit-ai/metagit-cliWrote 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/metagit-ai/metagit-cli/metagit-agent-coordination)<a href="https://agentmods.dev/skills/metagit-ai/metagit-cli/metagit-agent-coordination"><img src="https://agentmods.dev/badge/skills/metagit-ai/metagit-cli/metagit-agent-coordination/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/metagit-ai/metagit-cli/metagit-agent-coordination"><img src="https://agentmods.dev/badge/skills/metagit-ai/metagit-cli/metagit-agent-coordination.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.00070 | $0.01426 |
| Opus 5 | $0.00035 | $0.00713 |
| Sonnet 5 | $0.00014 | $0.00285 |
| Haiku 4.5 | $0.00007 | $0.00143 |
Grade A, and why
metagit-agent-coordination 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metagit Agent Coordination Layer (ACL)
Use when more than one agent may edit the same repository, or when an orchestrator must give each agent an exclusive checkout.
Full reference: docs/reference/agent-coordination.md
Task graphs (metagit task …) can store ACL command hints on nodes via
metagit task bind-acl without running git — see
docs/reference/task-graph.md.
Merge orchestration (metagit merge …) records conflicts with ACL command
hints only; it does not allocate branches or worktrees automatically.
The agent scheduler (metagit schedule next) scores ready task nodes and
returns dispatch hints without launching models or mutating git — see
docs/reference/agent-scheduler.md.
For a composed operator snapshot and next-work envelope across ACL + task
graph + optional 0009–0012, use skill metagit-aos
(metagit aos|coord status|doctor|next) — see
docs/reference/aos.md.
When to use
- Dispatching parallel subagents on the same repo
handoff.acl_commandsappears inmetagit agent dispatch-plan- Preventing two agents from sharing a working directory
- Declaring intended file paths before coding (advisory claims)
- Cleaning up expired leases / orphan worktrees
Do not confuse with handoff leases
| Concept | Command | Owns |
|---|---|---|
| Handoff claim TTL | metagit context handoff claim --ttl |
Task-queue row |
| ACL branch lease | metagit lease acquire |
agent/* branch |
Happy path
export METAGIT_AGENT_MODE=true
# 1. Allocate an exclusive agent branch
metagit branch allocate \
--repository project/repo \
--agent-id agent-1 \
--task-id 412 \
--description auth \
--json
# 2. Lease it (default TTL 30m; renew while working)
metagit lease acquire \
--repository project/repo \
--agent-id agent-1 \
--task-id 412 \
--allocate \
--ttl 30m \
--json
# 3. Create an isolated worktree (requires active lease)
metagit worktree create \
--repository project/repo \
--agent-id agent-1 \
--task-id 412 \
--branch agent/412-auth \
--json
# 4. Optional: advisory file claims before editing
metagit claim declare \
--repository project/repo \
--agent-id agent-1 \
--pattern 'src/auth/*' \
--json
# 5. Show execution manifest written on create
metagit worktree manifest agent-1
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 · 155 lines · 70 tokens per session scan A c4de96bc0b42
metagit-agent-coordination is a skill published in the GitHub repository metagit-ai/metagit-cli (3 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,426 once invoked, about $0.0003 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
clawrium-release-announcements
Daily — draft a release blog post, open a PR, iterate on comments until merged.
blog-author
Watch ric03uec/clawrium release tags; draft a short blog post per user-visible feature as a PR against blog/.
release-watcher
Watch upstream Claw releases and clawrium discussions; surface top 3 feature candidates to Devashish via Discord DM for approve/skip.
perseus
Use when you need a bounded, local Perseus context render before an assistant reads project state. Perseus resolves selected workspace inputs such as git, services, sessions, and task notes into markdown. Use for deterministic session starts, workspace audits, and explicit context handoffs.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.