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-phases-engine/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-phases-engine)<a href="https://agentmods.dev/skills/symphos-ai/orcho-core/orcho-core-phases-engine"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-core-phases-engine/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-phases-engine"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-core-phases-engine.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.00083 | $0.00472 |
| Opus 5.5 | $0.00033 | $0.00189 |
| Sonnet 5.5 | $0.00017 | $0.00094 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
orcho-core-phases-engine 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 2mo 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
Orcho Core Phases Engine
Own phase lifecycle, DAG execution, phase handlers, and per-phase bookkeeping.
First Reads
orcho-core/AGENTS.mdorcho-core/docs/architecture/phase_lifecycle.mdorcho-core/docs/architecture/execution_modes.mdorcho-core/pipeline/phases/orcho-core/pipeline/project/run.py- changed phase handler or DAG module
Owns
- phase handler registration and invocation
- phase lifecycle transitions
StepOutcomehandling- DAG/subtask execution
- subtask receipts and done-criteria attestation
- phase handoff and repair routing glue
- phase-end bookkeeping
Does Not Own
- parser/gate verdict meaning ->
orcho-core-quality-gates - runtime adapter invocation ->
orcho-core-runtime-session - prompt contract text ->
orcho-prompt-engine - public SDK/MCP payload shape ->
orcho-core-sdk-wire
Invariants
- Keep public app modules thin; lifecycle logic belongs in focused modules.
- Do not add new responsibilities to overloaded orchestration bodies.
- Preserve phase naming scheme.
- Phase changes that affect public state need SDK/MCP awareness.
Verification
- From
orcho-core: run targeted phase handler tests for the changed phase. - From
orcho-core:python -m pytest -q tests/unit/pipelinewith a focused-kfor subtask/DAG/phase lifecycle. - Run a mock project acceptance smoke when lifecycle sequencing changes.
- Pair with SDK/MCP tests for public phase-state changes.
Neighbor Skills
orcho-core-quality-gatesfor gate/parser verdict semanticsorcho-core-runtime-sessionfor runtime adapter/session behaviororcho-core-sdk-wirefor public phase state
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.
- 2mo ago First seen · 55 lines · 83 tokens per session scan A 0cad86c48b88
orcho-core-phases-engine is a skill published in the GitHub repository symphos-ai/orcho-core (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 83 tokens to every session and 472 once invoked, about $0.0003 per session on Opus 5.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
supermux-core
Use when building an app, script, bot or service in TypeScript that drives Claude Code, Codex, Cursor, OpenCode, Grok Build or Antigravity through the @supermux/core library.
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.