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 caoyuan-fire/engi-foundry-skill --skill engifoundry-orchgit clone --depth 1 https://github.com/caoyuan-fire/engi-foundry-skillWrote 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/caoyuan-fire/engi-foundry-skill/engifoundry-orch)<a href="https://agentmods.dev/skills/caoyuan-fire/engi-foundry-skill/engifoundry-orch"><img src="https://agentmods.dev/badge/skills/caoyuan-fire/engi-foundry-skill/engifoundry-orch/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/caoyuan-fire/engi-foundry-skill/engifoundry-orch"><img src="https://agentmods.dev/badge/skills/caoyuan-fire/engi-foundry-skill/engifoundry-orch.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.00052 | $0.01727 |
| Opus 5 | $0.00026 | $0.00864 |
| Sonnet 5 | $0.00010 | $0.00345 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
engifoundry-orch 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EngiFoundry Orch
<project-root> is the root of the target project. It normally contains engifoundry.config.json; the Router-authorized unconfigured fallback direct path is the only exception. <orch-skill-root> is the directory containing this SKILL.md. These are independent locations: never infer the project root from the Skill installation path, and never look for bundled Orch resources under the project root.
For configured work, read <project-root>/engifoundry.config.json, the project-owned workspace guide, the Workflow config, and <orch-skill-root>/references/contracts.md before writing records. For package, also read the complete Executor/Reviewer config and schema. Every Planning Review uses the configured Reviewer under engifoundry-review.
For the Router-authorized unconfigured fallback direct path, read only <orch-skill-root>/references/contracts.md. Use .engifoundry/packages/, create or reuse PHASE-001, and create only a direct PAK with one concise Job. Do not run Audit or create project configuration, workspace, Workflow, Executor, Reviewer, Package, or delivery records. These sparse paths are compatible with later Init adoption. Inline fallback never reads Orch.
Boundary
The Agent applies this contract to turn a classified task goal into execution input. While doing so, it does not select an Executor, edit implementation, perform delivery verification, or close delivery.
For configured new work, Router reads engifoundry-audit before selecting Orch:
direct: create the minimal PAK and one Job requirement contract, then the controlling Agent implements it under Router Group Rules and closes it through Verify.package: the Agent applies this contract to create execution input.
inline and blocked do not read Orch. Do not re-audit a supplied classification or explicit continuation of an existing PAK or Job.
executionMode is authoritative and is never inferred from files or field count. migration, or a missing mode with confirmed migration provenance, is preserved without Review, challenge, or runtime activation.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 74 lines · 52 tokens per session scan A dff7d9e03df9
engifoundry-orch is a skill published in the GitHub repository caoyuan-fire/engi-foundry-skill (2 stars, last pushed 16d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,727 once invoked, about $0.0003 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
julilaoshi-design
Public-safe julilaoshi-design workflow for official Pencil MCP execution and the free browser-first julilaoshi-design Web 2.0 editor. Use when a task needs Pencil handshake/canvas edits, .pen execution, screenshot review, or lightweight HTML design-to-web tweaking without redistributing official Pencil or leaking…
x-insight-cards
Run scheduled or manual creator curation that turns recent high-quality X posts into verified image-and-caption packs for Douyin and Xiaohongshu review, with optional private delivery to a pinned WeChat iLink bot review chat or confirmed File Transfer Assistant self-chat. Use when Codex needs to discover, verify…
zhuoyu-workshop
Student project delivery and packaging workflow for Codex. Use when the user needs help with Chinese university student projects, course projects, innovation training projects, competitions, capstones, graduation projects, project defense decks, closing reports, README/GitHub showcase materials, software copyright…
project-engineering-strategy
Use when a software project needs durable cross-session governance for formal documents, WBS or tracker coordination, worktree delivery boundaries, evidence and acceptance states, handoffs, or architecture and design-document control.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
xiaohongshu-conversion-path
A Xiaohongshu conversion-path guide maps how people move from seeing content on Xiaohongshu, a Chinese social-content platform, to taking a next step such as messaging, booking, trying a tool, or buying.