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.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/instructions/symphos-ai/orcho-core/agents-md)<a href="https://agentmods.dev/instructions/symphos-ai/orcho-core/agents-md"><img src="https://agentmods.dev/badge/instructions/symphos-ai/orcho-core/agents-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.1 | $0.02142 | $0.02142 |
| Opus 5 | $0.01071 | $0.01071 |
| Sonnet 5 | $0.00428 | $0.00428 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
orcho-core AGENTS.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 6d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orcho-core Instructions
Scope
This file applies to orcho-core/.
orcho-core is the Apache-2.0 public pipeline engine. It owns phases, agent
runtimes, registries, profiles, DAG execution, evidence, and CLI entry points.
It must remain independent from every other package in the workspace.
Also obey the workspace-level ../AGENTS.md.
Workspace Development Pipeline
When working on this repo inside the Orcho workspace, follow
../DEVELOPMENT_PIPELINE.md. That manual pipeline governs direct source
development only; it is separate from Orcho-managed worktree runs.
Stable Install Is Read-Only
Stable Orcho is a pipx install (venv at $HOME/.local/pipx/venvs/orcho,
shims in $HOME/.local/bin). Do not edit files inside that venv directly.
Change the canonical workspace repos and promote with orcho-promote; touch
the stable install only when the user explicitly asks to debug or repair it.
Build, Run, And Test
pip install -e ".[dev]"
pytest # final readiness, not the inner loop
pytest -k <name> # targeted test selection
pytest -q -m "not e2e and not packaging" # broad non-scenario gate
ruff check .
orcho ...
orcho-run ...
orcho-cross ...
Use --mock for tests or smoke runs that need a real subprocess but not a real
model. It swaps the agent provider for MockAgentProvider, avoiding LLM cost
and keeping the pipeline fast.
Run focused tests for narrow changes. Run the broader suite when touching shared
contracts, schemas, CLI behavior, phase orchestration, or cross-repo interfaces.
For orcho-core, cost markers (e2e, slow_process, git_worktree,
filesystem_heavy) explain why tests are expensive; serial means
xdist-unsafe. Pick one relevant slice instead of running every marker. Routine
escalation is targeted path/marker -> pytest -q -m "not e2e and not packaging"
-> final pytest -q; do not run the broad non-e2e gate immediately before the
full suite unless you expect it to fail faster and guide a fix.
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.
- 6d ago First seen · 218 lines · 2,142 tokens per session scan A 649c060e31ba
orcho-core AGENTS.md is an instructions file published in the GitHub repository symphos-ai/orcho-core (5 stars, last pushed today), licensed Apache-2.0. It adds 2,142 tokens to every session, about $0.0107 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.