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 agentmods add instructions/kninetimmy/orch/claude-mdgit clone --depth 1 https://github.com/kninetimmy/orchWrote 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/instructions/kninetimmy/orch/claude-md)<a href="https://agentmods.dev/instructions/kninetimmy/orch/claude-md"><img src="https://agentmods.dev/badge/instructions/kninetimmy/orch/claude-md.svg" alt="Measured on agentmods" 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 | $0.00402 | $0.00402 |
| Opus 5 | $0.00201 | $0.00201 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
orch CLAUDE.md 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 4d 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.
This is a copy
100% identical to orch AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Orch
A cross-host development orchestrator for Claude Code, Codex CLI, and OpenCode V2.
Session Continuity
memhub is the source of truth at .memhub/project.sqlite. The rendered files
under .memhub/rendered/ are the local human-readable view — generated from
the DB and gitignored by default. Re-render after /wrap-up with
memhub render. Read PROJECT.md at session start before acting.
Build / test / run
Shared core is Go (module github.com/kninetimmy/orch, Go 1.26+).
- Build:
go build ./... - Test:
go test ./... - Vet:
go vet ./... - Format:
gofmt -w .(CI fails on unformatted files) - Run:
go run ./cmd/orch status(ordoctor,help)
Host adapters under adapters/ are non-Go artifacts. Claude Code and Codex
CLI share the root marketplace manifest; OpenCode V2 uses the local npm package
at adapters/opencode/ and the beta opencode2 runtime.
This file is partially managed by Orch (see .orchestrator/config.toml).
- In Assist mode, tracked-file changes are mechanically denied; a mutating request triggers read-only planning instead.
- In Delivery mode, work happens in an isolated per-issue worktree, never in this checkout directly.
- Model/effort routing, concurrency, and host plugin setup live in
.orchestrator/config.toml— edit that file, not this block. - Orch upgrades this block through Delivery. Do not hand-edit it; a hand edit blocks the next install/upgrade until reverted or removed.
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.
- 4d ago First seen · 37 lines · 402 tokens per session scan A b07de49764e9
orch CLAUDE.md is an instructions file published in the GitHub repository kninetimmy/orch (21 stars, last pushed 7d ago), licensed MIT. It adds 402 tokens to every session, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to orch AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.