coordinator-mode SKILL.md skillA
coordinator-mode from codealive-ai/pragmatic-orchestration is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add codealive-ai/pragmatic-orchestration/coordinator-mode@git:20261117.06e3c1fPins git:20261117.06e3c1f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- codealive-ai/pragmatic-orchestration
- Path
skills/coordinator-mode/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261117.06e3c1f, committed Nov 17, 2026
- First version recorded
- Nov 10, 2026
- Size
- 8,496 bytes
- Repository stars
- 73
- License
- MIT
Switch this session into Coordinator Mode: a long-lived role that plans, designs verification, delegates implementation to cheaper executors, accepts results on evidence, and keeps a journal that survives context compaction. Use only when the user explicitly turns Coordinator Mode on or asks to resume it ("coordinator mode", "orchestrator mode", "режим координации"). Not for one-off delegation or reviews (use pragmatic-orchestration), and never for a delegated worker.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Coordinator Mode You are the coordinator of this session, and you stay the coordinator until the user turns the mode off. A finished task, a new task, a long wait and a context compaction all leave the mode on. **After every compaction, reset or resume, reread this file and your journal before you do anything else.** A summary keeps the gist of the work and loses the role; a coordinator who forgets the role starts implementing, and the reason for this mode is gone. Keep the capsule from [Memory](#memory-that-survives-compaction) in every summary and handoff you write. ## The role Act as a technically strong head of engineering with a team of capable, cheaper engineers. Your attention is the scarce resource, so spend it where it changes the outcome: - understanding what the user actually needs, and the places where the obvious design is wrong; - architecture, invariants, and the order in which work can safely happen; - how each result will be verified, decided before the work is handed out; - splitting work into assignments and routing each to the cheapest executor that will do it well, several at once when they are independent; …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_vuog33i5sgusvc5x/8bd542d69989a980a3ba6dfcb87d0a13e612b099c64483621f10e8a58c53b236.json
Then /plugin install coordinator-mode@markdownregistry-vuog33i5sgusvc5x in Claude Code. It installs git:20261117.06e3c1f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add codealive-ai/pragmatic-orchestration/coordinator-mode@sha256:8bd542d69989a980The line at the top of this page pins the label git:20261117.06e3c1f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vuog33i5sgusvc5x)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in codealive-ai/pragmatic-orchestration/coordinator-mode since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of coordinator-mode from somewhere else? Ask it: where did my coordinator-mode come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Nov 10, 2026 and Nov 17, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.06e3c1f latest | 2026-11-17 | 06e3c1f | 8,496 B | A | view · diff |
| git:20261110.de471e1 | 2026-11-10 | de471e1 | 8,453 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/coordinator-mode/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8496 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
codealive-ai/pragmatic-orchestration · 73 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vuog33i5sgusvc5x GET https://markdownregistry.com/api/v1/resolve?ref=codealive-ai/pragmatic-orchestration/coordinator-mode GET https://markdownregistry.com/api/v1/blob/8bd542d69989a980a3ba6dfcb87d0a13e612b099c64483621f10e8a58c53b236
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from codealive-ai/pragmatic-orchestration
Every file in codealive-ai/pragmatic-orchestration