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-cli-ux/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-cli-ux)<a href="https://agentmods.dev/skills/symphos-ai/orcho-core/orcho-core-cli-ux"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-core-cli-ux/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-cli-ux"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-core-cli-ux.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.00091 | $0.00424 |
| Opus 5 | $0.00046 | $0.00212 |
| Sonnet 5 | $0.00018 | $0.00085 |
| Haiku 4.5 | $0.00009 | $0.00042 |
Grade A, and why
orcho-core-cli-ux 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.
What it actually says
Orcho Core CLI UX
Keep the CLI a thin, stable facade over SDK and pipeline boundaries.
First Reads
orcho-core/AGENTS.mdorcho-core/core/io/AGENTS.mdwhen stdout/stderr, ANSI, TTY, or prompts changeorcho-core/cli/- relevant
orcho-core/tests/unit/cli/test_*.py
Owns
- CLI command wiring
- help text and epilogs
- output modes
- stdout/stderr formatting
- transcript rendering
- interactive prompts
- latest/resume UX
Does Not Own
- pipeline semantics -> relevant core specialist
- SDK payload shape ->
orcho-core-sdk-wire - MCP exposure ->
orcho-mcp - public wording hygiene ->
orcho-public-boundary
Invariants
- CLI handlers stay thin: parse args, call delegate, format, print, return code.
- stdout is intended output; errors go to stderr where appropriate.
--stream-outputand--verbosesemantics stay stable.- Preserve byte-level expectations where tests assert them.
Verification
python -m pytest -q orcho-core/tests/unit/cli- command-specific tests for changed commands
- public boundary scan for help/docs wording
Neighbor Skills
orcho-core-sdk-wirewhen formatter inputs or public status/evidence shape changeorcho-public-boundaryfor public help/docs/error wordingorcho-core-evidence-observabilitywhen CLI renders evidence internals
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 · 52 lines · 91 tokens per session scan A 300cf330892e
orcho-core-cli-ux is a skill published in the GitHub repository symphos-ai/orcho-core (5 stars, last pushed today), licensed Apache-2.0. It adds 91 tokens to every session and 424 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.