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.
git clone --depth 1 https://github.com/architonixlabs/RepoOrchWrote 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/plugins/architonixlabs/repoorch/repoorch)<a href="https://agentmods.dev/plugins/architonixlabs/repoorch/repoorch"><img src="https://agentmods.dev/badge/plugins/architonixlabs/repoorch/repoorch/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/plugins/architonixlabs/repoorch/repoorch"><img src="https://agentmods.dev/badge/plugins/architonixlabs/repoorch/repoorch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 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
{
"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"
}
What it installs
The manifest is a name and a version. 3 skills, 8 commands, 2 agents, 2 hooks travel with it, and installing the plugin installs all of them — 688 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill routing A 33 tokens
- Skill workspace-knowledge A 91 tokens
- Skill repo-indexing B 33 tokens
- Command repo-orch-deliberate A 62 tokens
- Command repo-orch-init A 53 tokens
- Command repo-orch-status A 39 tokens
- Command repo-orch-sync A 34 tokens
- Command repo-orch-edit A 29 tokens
- Command repo-orch-triage B 53 tokens
- Command repo-orch-setup B 59 tokens
- Command repo-orch-graph B 61 tokens
- Agent repo-{{NAME}} A 74 tokens
- Agent repo-orch-master A 67 tokens
- Hook SessionStart A not measured
- Hook PreToolUse A not measured
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.
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 · 13 lines scan A adfbf57d900b
repo-orchestrator is a plugin published in the GitHub repository architonixlabs/RepoOrch (3 stars, last pushed 4mo 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.
Other plugins, from other repositories
pm
GitHub issue lifecycle: brainstorm design approaches, create structured issues for LLM agent teams, triage and recommend next issues, audit and clean up stale backlogs, and deep-validate individual issues against the codebase.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
product-management
Product management specialists for PRD writing, content creation, and project planning. Tools for product managers and technical writers.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
commander-hub marketplace
Plugin marketplace listing 1 plugin: commander.
radin
Cost-optimized agentic workflow stack for solo devs: backlog orchestration (radin-batch, radin-plan, radin-review) plus curated companion tools.