Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/architonixlabs/RepoOrchnpx agentmods add commands/architonixlabs/repoorch/repo-orch-initWrote 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/commands/architonixlabs/repoorch/repo-orch-init)<a href="https://agentmods.dev/commands/architonixlabs/repoorch/repo-orch-init"><img src="https://agentmods.dev/badge/commands/architonixlabs/repoorch/repo-orch-init/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/commands/architonixlabs/repoorch/repo-orch-init"><img src="https://agentmods.dev/badge/commands/architonixlabs/repoorch/repo-orch-init.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.00053 | $0.02419 |
| Opus 5 | $0.00026 | $0.01210 |
| Sonnet 5 | $0.00011 | $0.00484 |
| Haiku 4.5 | $0.00005 | $0.00242 |
Grade A, and why
repo-orch-init 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 10d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repo-orch-init
Bootstrap the repo-orchestrator for your workspace. Run this once from your workspace root (the directory that contains your service repos as immediate subdirectories).
What this command does
- Discovers all repos under the workspace root
- Indexes each repo (language, frameworks, endpoints, events, dependencies)
- Writes an editable context document per repo — then stops for your review
- On your confirmation: generates specialist agents (each with a unique name and a per-repo skill file) and updates
registry.json
Step 1 — Discover repos
Read .repo-orchestrator/config.json if it exists. If it does not exist, create it with this default content:
{
"discovery": {
"mode": "auto",
"root": ".",
"exclude": [".git", ".claude", ".repo-orchestrator", "node_modules"]
}
}
If mode is "auto":
List all immediate subdirectories of root. Keep the ones that contain a .git directory (or are listed in .git/modules, indicating a submodule). Remove any directory whose name appears in exclude.
If mode is "list":
Use the repos array as-is. Do not scan. For any entry whose path starts with a URL (e.g., https://):
- Ask the user explicitly: "Clone
<url>into<local-path>? This requires a network connection and will write to your filesystem. [y/N]" - Do not clone without explicit confirmation.
If no repos are discovered, stop: "No git repositories found as immediate subdirectories of <root>. Check your workspace layout or switch to mode: list in .repo-orchestrator/config.json."
Step 2 — Index each repo
For each discovered repo, try the Tier-1 indexer first:
node indexer/dist/index.js <repoPath>
If this command succeeds (exit code 0), parse the JSON output as facts. If it fails or the file does not exist, fall back to Tier-0 indexing using the repo-indexing skill (skills/repo-indexing/SKILL.md).
Apply the budget rule from that skill. Do not read every file. Extract: languages, frameworks, owns, endpoints, emits, consumes, dependsOn, providesTo, fingerprint.
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.
- 10d ago First seen · 261 lines · 53 tokens per session scan A 2a5a020dd77b
repo-orch-init is a command published in the GitHub repository architonixlabs/RepoOrch (3 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 2,419 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 commands, from other repositories
proof-report
Generate a Launch Proof Report for an existing repo by combining release, publish, and security audit evidence.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
release
Generate changelog, bump version, and create git tag.