Borrowing it
Nothing to install: this file belongs to symphos-ai/orcho-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/symphos-ai/orcho-core/main/.agents/skills/orcho-core-router/SKILL.mdgit clone --depth 1 https://github.com/symphos-ai/orcho-coreWrote 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/symphos-ai/orcho-core/orcho-core-router)<a href="https://agentmods.dev/skills/symphos-ai/orcho-core/orcho-core-router"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-core-router/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/skills/symphos-ai/orcho-core/orcho-core-router"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-core-router.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.00099 | $0.00795 |
| Opus 5 | $0.00049 | $0.00398 |
| Sonnet 5 | $0.00020 | $0.00159 |
| Haiku 4.5 | $0.00010 | $0.00080 |
Grade A, and why
orcho-core-router 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orcho Core Router
Route ambiguous orcho-core work to one primary specialist. Do not implement
here and do not deep-read ADRs here.
Owns
- subdomain selection inside
orcho-core - pair-load decisions when a change crosses two core surfaces
Does Not Own
- implementation
- deep ADR reading
- explicit file tasks that already name a specialist-owned subsystem
First Reads
/Users/smartgamma/www/orcho/orcho-core/AGENTS.mdorcho-core/docs/creator/02_package_structure.mdorcho-core/docs/creator/05_core_subdomains.md
Decision Table
| Task area | Specialist |
|---|---|
prompt files, prompt contracts, cache layout, _prompts |
orcho-prompt-engine |
| runtime invocation, sessions, adapters, agent runtimes | orcho-core-runtime-session |
phase lifecycle, phase handlers, DAG/subtasks, StepOutcome |
orcho-core-phases-engine |
| plan/review/release parsers, gate semantics, halt/resume | orcho-core-quality-gates |
| evidence bundles, events, metrics, run diff, artifacts | orcho-core-evidence-observability |
| sandbox, isolation setup, dirty intake, worktrees | orcho-core-isolation-worktrees-sandbox |
| shared test infra, fixtures, golden snapshots, pytest config | orcho-core-test-infra-goldens |
| cross-project handoff, contract check, final bundle | orcho-core-cross-project |
| profiles, operating modes, plugin entry points | orcho-core-profiles-plugins |
| skill discovery, trust, injection, roster, traceability | orcho-core-skills-registry |
| SDK schema, public payload, MCP-visible core shape | orcho-core-sdk-wire |
| CLI commands, help, output formatting, terminal UX | orcho-core-cli-ux |
Cross-Domain Pairs
- parser output exposed publicly ->
orcho-core-quality-gates+orcho-core-sdk-wire - evidence exposed publicly ->
orcho-core-evidence-observability+orcho-core-sdk-wire - cross final acceptance ->
orcho-core-cross-project+orcho-core-quality-gates - runtime prompt/session shape ->
orcho-core-runtime-session+orcho-prompt-engine - skill trace exposed through MCP ->
orcho-core-skills-registry+orcho-mcp+ maybeorcho-core-sdk-wire
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 · 73 lines · 99 tokens per session scan A 040d5a88d7e9
orcho-core-router is a skill published in the GitHub repository symphos-ai/orcho-core (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 99 tokens to every session and 795 once invoked, about $0.0005 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
review-deep
Drive the deep-review phase of an automated PR review. Consumes the walkthrough, runs the deterministic deep-review workflow (parallel lenses → adversarial validation → code-enforced threshold/caps), drafts the surviving findings, and completes the review run.
review-orchestrator
Drive an automated PR review. Produces a structured walkthrough plus inline draft comments via the octomux review CLI. NEVER posts to GitHub directly — publishing is human-gated.
review-pr
Use when reviewing a pull request, posting PR review comments, or when user says /review-pr. Reviews code with parallel agents and posts a pending GitHub review with inline comments.
review-walkthrough
Drive the walkthrough phase of an automated PR review. Produces a structured walkthrough JSON only — no inline comment drafts. The deep-review agent is attached automatically by the server after this agent finishes.
create-pr
Use when creating a pull request, opening a PR, or pushing and creating a PR for an octomux task.
ship-pr
Use to ship a change end-to-end from an octomux task — write a walkthrough, gate on a code review, open the PR, then monitor CI/comments and push fixes, finally refreshing the walkthrough. Heavier than create-pr; use when you want the full review→ship→watch loop, not just opening a PR.