What is repo-orch-status?

A status command for a repo-orchestrator workspace, showing registered repositories and whether their supporting files and summaries are available.

Use it to review index times, knowledge-graph availability, edited-context flags, and whether specialist files and Agent Teams support are enabled.

It lets you quickly check whether setup is working and identify repositories that need indexing or attention.

repo-orch-status — Command for Claude Code by architonixlabs

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.

Clone the repo

git clone --depth 1 https://github.com/architonixlabs/RepoOrch

Made for: Claude Code.

Or install repo-orchestrator, the plugin that ships this one along with the rest of its 3 skills, 8 commands, 2 agents, 2 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/architonixlabs/repoorch/repo-orch-status/github.svg)](https://agentmods.dev/commands/architonixlabs/repoorch/repo-orch-status)

Your own site

<a href="https://agentmods.dev/commands/architonixlabs/repoorch/repo-orch-status"><img src="https://agentmods.dev/badge/commands/architonixlabs/repoorch/repo-orch-status/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/architonixlabs/repoorch/repo-orch-status"><img src="https://agentmods.dev/badge/commands/architonixlabs/repoorch/repo-orch-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,242 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00039	$0.01242
Opus 5	$0.00019	$0.00621
Sonnet 5	$0.00008	$0.00248
Haiku 4.5	$0.00004	$0.00124

Measured 11d ago against content hash 11df9d8c2649, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

repo-orch-status 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 11d 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.

commands/repo-orch-status.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/repo-orch-status

Show a concise status dashboard for the current repo-orchestrator workspace. Use this to verify setup is working, to see when repos were last indexed, and to spot repos that need attention.

Step 1 — Load the registry

Read .repo-orchestrator/registry.json. If it does not exist, output:

┌── repo-orchestrator ─────────────────────────────────────────┐
│  No registry found.                                          │
│                                                              │
│  Run /repo-orch-setup  (first time)                          │
│  Run /repo-orch-init   (skip setup wizard)                   │
└──────────────────────────────────────────────────────────────┘

Stop here.

Step 2 — Gather supplementary facts

For each repo entry in the registry, check:

Context file exists: does .repo-orchestrator/context/<name>.md exist?
Graph exists: does .repo-orchestrator/graphs/<name>/ exist and contain at least one file?
Skill file exists: does .repo-orchestrator/skills/<name>.md exist?
Agent file exists: does .claude/agents/repo-<name>.md exist?
userEdited flag: read from registry entry (default false)
lastIndexed timestamp: read from registry entry; format as relative time if recent (e.g., "3 days ago"), or ISO date if older than 30 days

Also check:

Agent Teams: read .claude/settings.json; check env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS === "1" and experimental.teammateMode === true
Tier-1 indexer: does .claude/plugins/repo-orchestrator/indexer/dist/index.js exist?
Tier-2 MCP server: does .claude/plugins/repo-orchestrator/mcp/dist/server.js exist?

Step 3 — Print the dashboard

═══════════════════════════════════════════════════════════════
repo-orchestrator  status
═══════════════════════════════════════════════════════════════

Infrastructure
──────────────────────────────────────────────────────────────
  <icon>  Agent Teams          <detail>
  <icon>  Tier-1 indexer       <detail>
  <icon>  Tier-2 MCP server    <detail>

Registered repos  (<N> total)
──────────────────────────────────────────────────────────────
  Repo               Last indexed      Context  Graph  Skill  Agent  Flags
  ──────────────────────────────────────────────────────────
  <name>             <relative-time>   <icon>   <icon> <icon> <icon> <flags>
  <name>             <relative-time>   <icon>   <icon> <icon> <icon> <flags>
  ...

Legend:  ✓ present   ✗ missing   ○ optional/not built
Flags:   [edited] = context file has user edits (re-sync recommended)
         [no-owns] = owns field is empty (routing will miss this repo)
         [stale] = last indexed > 7 days ago

──────────────────────────────────────────────────────────────

Read the full file on GitHub · 126 lines

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.

11d ago First seen · 126 lines · 39 tokens per session scan A 11df9d8c2649

Subscribe to this mod's changes

repo-orch-status is a command published in the GitHub repository architonixlabs/RepoOrch (3 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 1,242 once invoked, about $0.0002 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.

Claude Code Git and workflow agent-teams ai-agents claude-code-plugin devtools microservices

repo-orch-status

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/repo-orch-status

Step 1 — Load the registry

Step 2 — Gather supplementary facts

Step 3 — Print the dashboard

What this file has done since we first saw it

Other commands, from other repositories

proof-report

audit-release

context

git

composite-actions

release