repo-orchestrator

A plugin that coordinates AI agents working across several code repositories, typically separate services in a microservice project. It creates proposed plans for changes that affect more than one repository.

In plain words
What is it for?
Use it to coordinate multi-repository planning, impact analysis, and contract checks for tickets or incidents. It proposes plans but does not apply them.
Why use it?
It helps trace cross-repository effects and service contracts before development begins, while leaving the actual file changes to you.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add architonixlabs/RepoOrch
agentmods
npx agentmods add plugins/architonixlabs/repoorch/repoorch
Clone the repo
git clone --depth 1 https://github.com/architonixlabs/RepoOrch

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

repo-orchestrator 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 2d 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.

.claude-plugin/plugin.json · 13 lines

What it actually says

{
  "name": "repo-orchestrator",
  "version": "0.3.0",
  "description": "Turns a multi-repo microservice project into a coordinated AI agent team that proposes (never applies) cross-repo change plans.",
  "author": {
    "name": "Architonix",
    "url": "https://github.com/architonixlabs"
  },
  "license": "MIT",
  "keywords": ["multi-repo", "microservices", "agent-teams", "orchestration", "planning"],
  "repository": "https://github.com/architonixlabs/RepoOrch"
}
Files

What ships with it

1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 2d ago First seen · 13 lines scan A adfbf57d900b

Subscribe to this mod's changes

repo-orchestrator is a plugin published in the GitHub repository architonixlabs/RepoOrch (3 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.