What is Orca-Orchestration AGENTS.md?

A project instruction file for Orca-Orchestration, a system that builds and displays task DAGs. A DAG is a set of tasks connected in dependency order, and the file covers both the orchestration skill and its server-and-web viewer.

Use it when developing the Orca DAG viewer, changing its Express or React Flow parts, or updating instructions for creating orchestration task graphs.

It explains the repository layout, commands, and important behavior that may not be obvious from the code. This helps agents edit the published instructions or the separate server and web modules safely.

How ZinkLu/Orca-Orchestration configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to ZinkLu/Orca-Orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ZinkLu/Orca-Orchestration/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/ZinkLu/Orca-Orchestration

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/zinklu/orca-orchestration/agents-md/github.svg)](https://agentmods.dev/instructions/zinklu/orca-orchestration/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/zinklu/orca-orchestration/agents-md"><img src="https://agentmods.dev/badge/instructions/zinklu/orca-orchestration/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/zinklu/orca-orchestration/agents-md"><img src="https://agentmods.dev/badge/instructions/zinklu/orca-orchestration/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,279 This file is loaded in full into every session.

When invoked 3,279 The same file — it is already loaded in full.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.03279	$0.03279
Opus 5.5	$0.01312	$0.01312
Sonnet 5.5	$0.00656	$0.00656
Haiku 4.5	$0.00328	$0.00328

Measured 1mo ago against content hash e53b98cd207e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

Orca-Orchestration AGENTS.md scanned grade C with 1 finding 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- `dist-npm/` — the staged npm package, rebuilt from scratch by `scripts/build-npm.mjs` (it `rm -rf`s the dir first). Never hand-edit; the `package.json` in there is generated.

AGENTS.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Guidance for agents working in this repo (editing the viewer/tooling or the skill doc). For using the skill to build DAGs, read skill/SKILL.md and README.md instead. CLAUDE.md is a symlink to this file — edit here, don't replace the link.

Project shape

Two independent modules in one npm-workspaces repo (workspaces: [server, web]):

skill/SKILL.md — a published agent skill (frontmatter + prose). Teaches an external agent to build an Orca orchestration task DAG via the orca CLI. No code; edit it like a doc, keep frontmatter intact.
server/ + web/ — the orca-dag viewer: an Express API + React Flow SPA that visualizes a Run's DAG and runs a self-driven coordinator loop. Compiles to a single portable binary (dist/orca-dag).

This repo is a thin, heavily-commented wrapper over the orca CLI. Every Orca quirk is documented in server/src/orca.ts comments — read them before touching orchestration code.

Commands

npm install
npm run dev            # BOTH server (:8787) + web (:5173) via concurrently; vite proxies /api → :8787
npm run dev:server     # tsx watch src/index.ts (server only)
npm run dev:web        # vite (web only)
npm run build          # web only: tsc -b && vite build → web/dist
npm run build:binary   # web build → embed as base64 in server/src/generated/webAssets.ts → bun --compile → dist/orca-dag
npm run build:npm      # web build → esbuild the server → dist-npm/ (the publishable `orca-dag` package; Node only, no Bun)
npm start              # server (tsx) against web/dist on disk; needs `npm run build` first for UI

No lint, test, or typecheck scripts exist. Typecheck manually:
- web: npm run build -w web (runs tsc -b first, fails fast on type errors)
- server: npx tsc -p server/tsconfig.json --noEmit
build:binary requires bun on PATH (not declared as a dependency). Cross-compile with TARGET=bun-linux-x64 npm run build:binary.
Binary runtime env: PORT (8787), NO_OPEN=1 (skip browser), WORKSPACE_DIR (overrides active worktree), ORCA_WORKTREE (default active).

Read the full file on GitHub · 86 lines

Changes

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.

1mo ago First seen · 86 lines · 3,279 tokens per session scan C e53b98cd207e

Subscribe to this mod's changes

Orca-Orchestration AGENTS.md is an instructions file published in the GitHub repository ZinkLu/Orca-Orchestration (140 stars, last pushed 2mo ago), licensed MIT. It adds 3,279 tokens to every session, about $0.0131 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agents Planning

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

Orca-Orchestration: Instructions file for Codex

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade C, and why

Recursive force deletehighDestructive command

How it starts

AGENTS.md

Project shape

Commands

What this file has done since we first saw it

Other instructions, from other repositories

vscode buildNext.instructions.md

next.js AGENTS.md

vscode oss-third-party-notices.instructions.md

langchain AGENTS.md

vscode copilot-instructions.md

vscode model-prompts.instructions.md