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.
npx skills add architonixlabs/RepoOrch --skill routinggit 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/skills/architonixlabs/repoorch/routing)<a href="https://agentmods.dev/skills/architonixlabs/repoorch/routing"><img src="https://agentmods.dev/badge/skills/architonixlabs/repoorch/routing.svg" alt="Measured on agentmods" 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.00033 | $0.02248 |
| Opus 5 | $0.00016 | $0.01124 |
| Sonnet 5 | $0.00007 | $0.00450 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade A, and why
routing 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 7d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Routing Skill
Use this skill when the master controller needs to select which repo specialist agents to involve for a given ticket or incident description.
Goal
Given a ticket/incident text and the current registry.json, return a ranked list of candidate repos (cap at 5), each with a confidence score and a reason string. Pass both the routing decision and the confidence signal to each specialist agent.
Step 1 — Load the registry
Read .repo-orchestrator/registry.json. If it does not exist, stop: "Registry not found. Run /repo-orch-init first."
Extract the repos array. For each repo, the routing-relevant fields are:
| Field | Weight |
|---|---|
owns |
Primary routing signal — domain keywords the human-chosen routing vocabulary |
endpoints |
High-signal match — ticket paths map directly to code |
emits / consumes |
Event-level routing for async systems |
name |
Explicit repo name mentions in the ticket |
languages / frameworks |
Tech-specific fallback |
owner.team |
Team name mentions (e.g., "payments team", "Platform") |
Step 2 — Normalize the ticket text
2a. Tokenize
Split on whitespace and punctuation. Lowercase everything. Remove stop words: the a an is was were are be been being has have had do does did will would could should may might must can cannot.
2b. Acronym expansion table
Expand these before scoring. If a ticket token matches a key, add the expanded form as an additional token:
| Abbreviation | Expand to |
|---|---|
auth |
authentication, authorization |
authn |
authentication |
authz |
authorization |
jwt |
token, auth |
rbac |
roles, permissions, authorization |
acl |
permissions, access |
sso |
authentication, identity |
idp |
identity, authentication |
mfa |
authentication, security |
2fa |
authentication, security |
api |
endpoint, service |
cdn |
cache, static, assets |
db |
database, persistence |
pg |
postgres, database |
k8s |
kubernetes, infra, deploy |
ci |
build, pipeline |
cd |
deploy, pipeline |
sla |
availability, latency |
ux |
frontend, ui |
ui |
frontend |
fe |
frontend |
be |
backend |
ws |
websocket |
grpc |
rpc, service |
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.
- 7d ago First seen · 212 lines · 33 tokens per session scan A d65829309b7e
routing is a skill published in the GitHub repository architonixlabs/RepoOrch (3 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 2,248 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.
Other skills, from other repositories
writing-style
Structural pattern analysis for writing-mode review. Performs paragraph-level decomposition and pattern aggregation. Invoked by the team lead during editorial review.
pr-check
PR review compliance: fetch review comments from an open PR, categorize as resolved/unresolved/dismissed, critically evaluate fixable items, implement approved fixes, and reply inline. Pass --unattended to halt on human-judgment items (emitted as Pending-Human) instead of prompting via AskUserQuestion.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting. Runs specialized review agents, scores findings, and submits a GitHub PR review via post-review.sh. Always executes post-review.sh to submit a review on every run (including zero-findings runs). Triggers…
council
Consult external AI council (Gemini 3.8 Flash, Codex, GLM-5.3, Kimi) for thorough reviews and consensus-driven decisions. Use ONLY when explicitly invoked with "/council" or when user says "consult the council", "invoke council", or "council review". Do NOT auto-trigger on generic phrases like "thorough review".
pr-validity
PR validity analysis: fetch PR diff, extract new code additions, search existing codebase for duplicate or overlapping implementations, classify changes, and create a structured GitHub issue.
brainstorm
You MUST use this skill before /pm when work is ambiguous, scope is unclear, or multiple approaches exist. Explores problem space, proposes 2-3 approaches with trade-offs, and produces an approved spec document that feeds into both issue creation (/pm) and implementation planning (/cdt). Triggers: brainstorm, explore…