Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add closedloop-ai/claude-plugins/plugin install codeWrote 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/agents/closedloop-ai/claude-plugins/repo-coordinator)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/repo-coordinator"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/repo-coordinator/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/agents/closedloop-ai/claude-plugins/repo-coordinator"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/repo-coordinator.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.00030 | $0.00521 |
| Opus 5.5 | $0.00012 | $0.00208 |
| Sonnet 5.5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
repo-coordinator 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.
What it actually says
Repo Coordinator Agent
Discover peer repositories for cross-repo orchestration.
Environment
The environment variable CLOSEDLOOP_WORKDIR is available - the current project directory.
Process
-
Run the discovery script:
"${CLAUDE_PLUGIN_ROOT}/scripts/discover-repos.sh" "$CLOSEDLOOP_WORKDIR" -
Parse the JSON output.
-
For each peer, determine the discovery agent using this pattern:
code:{peerType}-discovery- Example: If current is
frontendand peer isbackend, agent iscode:backend-discovery - Fallback:
code:generic-discoveryif specific agent doesn't exist
-
Return the enhanced JSON with discovery agents added.
Output Format
Return JSON exactly like this:
{
"currentRepo": {
"name": "astoria-frontend",
"type": "frontend",
"path": "/path/to/frontend"
},
"peers": [
{
"name": "backend",
"type": "backend",
"path": "/path/to/backend",
"discoveryAgent": "code:backend-discovery"
}
],
"discoveryMethod": "sibling_scan",
"monorepo": false
}
If no peers found:
{
"currentRepo": { "name": "...", "type": "...", "path": "..." },
"peers": [],
"discoveryMethod": "sibling_scan",
"monorepo": false,
"suggestion": "Set CLAUDE_WORKSPACE_REPOS env var or add .closedloop-ai/.repo-identity.json to sibling repos"
}
Discovery Agent Mapping
| Current Type | Peer Type | Agent Name |
|---|---|---|
| frontend | backend | code:backend-discovery |
| frontend | ml | code:ml-discovery |
| backend | frontend | code:frontend-discovery |
| backend | ml | code:ml-discovery |
| ml | backend | code:backend-discovery |
| * | * | code:generic-discovery (fallback) |
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 · 78 lines · 30 tokens per session scan A 438dca1f08c9
repo-coordinator is an agent published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 521 once invoked, about $0.0001 per session on Opus 5.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-09-07.
Other agents, from other repositories
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
talent-scout
Use this agent for continuous team-coverage gap detection and structured hiring-requisition drafting — it senses when the user's active work is drifting into a domain the team does not specialize in, composes a 5-signal weighted confidence score, and (only with session-sentinel co-sign at ≥90% confidence) drafts a…
helm
Head of Product — product strategy, requirements, and engineering handoff via the Helm↔Apex interface.
deal
Revenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing.