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-prompt-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-prompt-engine)<a href="https://agentmods.dev/skills/symphos-ai/orcho-core/orcho-prompt-engine"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-prompt-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-prompt-engine"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-prompt-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.00077 | $0.00482 |
| Opus 5 | $0.00039 | $0.00241 |
| Sonnet 5 | $0.00015 | $0.00096 |
| Haiku 4.5 | $0.00008 | $0.00048 |
Grade A, and why
orcho-prompt-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 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.
What it actually says
Orcho Prompt Engine
Work safely on prompt composition, prompt contracts, cache layout, and prompt evidence. Keep machine contracts in code-owned prompt blocks, not loose prose.
First Reads
orcho-core/AGENTS.mdorcho-core/pipeline/prompts/AGENTS.mdorcho-core/core/_prompts/AGENTS.mdorcho-core/docs/adr/0009-composable-prompt-parts.mdorcho-core/docs/adr/0028-cache-first-physical-wire-layout.md- changed prompt builder/template files
Owns
pipeline/prompts/*core/_prompts/*- prompt part ordering and cache metadata
- prompt contract templates and protected system-tail policy
- prompt render evidence and prompt snapshots
Does Not Own
- runtime adapter invocation ->
orcho-core-runtime-session - SDK/MCP public payload shape ->
orcho-core-sdk-wire - parser/gate verdict semantics ->
orcho-core-quality-gates
Invariants
- Think in ordered prompt parts, not one rendered string.
- Preserve cache-stable prefix ordering unless deliberately changing it with tests.
- Put dynamic facts in typed prompt parts with explicit stability/cache scope.
- Keep protected contracts in code-owned templates.
- Do not silently widen editable markdown into protocol policy.
Verification
- From
orcho-core:python -m pytest -q tests/unit/pipeline/prompts - From
orcho-core:python -m pytest -q tests/unit/pipeline/runtime/test_snapshot_session_parity.pywhen cache/session behavior changes - Review prompt snapshot/golden diffs before accepting them.
Neighbor Skills
orcho-core-runtime-sessionwhen prompt/session continuity changesorcho-core-evidence-observabilitywhen rendered prompt data is persisted as evidenceorcho-labwhen evaluating prompt variants
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 · 53 lines · 77 tokens per session scan A dc2074599d59
orcho-prompt-engine is a skill published in the GitHub repository symphos-ai/orcho-core (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 482 once invoked, about $0.0004 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
prompt-tuning
Tune a prompt, or anything whose quality is measured by non-deterministic model output, without chasing noise - a noise baseline before the first edit, medians over repeated runs, enforcement AFTER generation rather than in the wording. Use when iterating on prompts or model-judged output.
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.