Borrowing it
Nothing to install: this file belongs to epicsagas/epic-harness. 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/epicsagas/epic-harness/main/AGENTS.mdgit clone --depth 1 https://github.com/epicsagas/epic-harnessWrote 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/epicsagas/epic-harness/agents-md)<a href="https://agentmods.dev/instructions/epicsagas/epic-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/epicsagas/epic-harness/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.
<a href="https://agentmods.dev/instructions/epicsagas/epic-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/epicsagas/epic-harness/agents-md.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.04765 | $0.04765 |
| Opus 5.5 | $0.01906 | $0.01906 |
| Sonnet 5.5 | $0.00953 | $0.00953 |
| Haiku 4.5 | $0.00477 | $0.00477 |
Grade A, and why
epic-harness 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 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.
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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
epic-harness
25 skills (9 pipeline + 16 quality) + self-evolving agent harness.
Structure
skills/— 25 skills +_dispatchrouter +_criticreviewerregistry/— Seeding resources (embedded in Rust binary at compile time)presets/— Cold-start skill templatesrules/— Seeded host rule filesscripts/install.js— Plugin bootstrap (SessionStart)
src/— Rust crate; single binary (epic-harness)src/hooks/— Ring 0 automation (guard, polish, observe, resume, snapshot, reflect)src/evolve/— Ring 3 evolution loop
docs/— User-facing documentation and assetsarchitecture.md,quickstart.md,demo/,references/,specs/
integrations/common/—HARNESS.mdembedded into the binary (include_str!), self-seeded to~/.harness/HARNESS.md
Architecture: 4-Ring Model
- Ring 0 (Autopilot): Hooks auto-maintain quality, restore sessions, learn
- Ring 1 (Pipeline): 9 skills that orchestrate multi-step workflows (discover → spec → go → audit → eval → ship, orbit, evolve, team)
- Ring 2 (Quality Gates): 17 skills that auto-trigger on context signals (tdd, debug, secure, threat-model, vuln-scan, triage, verify, etc.)
- Ring 3 (Evolve): Observe → Analyze → Evolve → Gate → Reload self-improvement loop
/orbit — Autonomous Pipeline
Single-command spec-to-PR execution with three entry modes.
flowchart TD
START["/orbit"] --> MODE{"requirement?"}
MODE -->|"unclear"| WAIT["Interactive\nUser runs /discover → /spec"]
MODE -->|"clear + complex"| COUNCIL["Council\n4-Voice Auto-spec"]
MODE -->|"clear + simple"| DIRECT["Direct\nAuto-spec"]
WAIT --> SPEC["Load Approved Spec"]
COUNCIL --> SPEC
DIRECT --> SPEC
SPEC --> GO["Go Phase\nPlan → Execute → Integrate"]
GO --> CHECK["Check Phase\nReview + Audit + Test"]
CHECK -->|"PASS"| SHIP["Ship Phase\nIsolated Test → PR → CI"]
CHECK -->|"WARN"| SHIP
CHECK -->|"FAIL"| RETRY{"retry < 3?"}
RETRY -->|Yes| FIX["Go Fix\nTarget fixes from action items"]
FIX --> CHECK
RETRY -->|No| PAUSE["Pause — User decides"]
PAUSE -->|continue| FIX
PAUSE -->|abort| ABORT["Abort"]
SHIP --> EVOLVE["Evolve\nAuto-analyze session"]
EVOLVE --> DONE["Orbit Complete\nConsolidated Report"]
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 Changed · +3 tokens per session 97aa5e620826
- 1mo ago Changed · +15 lines · +271 tokens per session eacda49977a1
- 1mo ago Changed · +15 lines · +238 tokens per session ca7612093217
- 1mo ago First seen · 342 lines · 4,253 tokens per session scan A 5695275eeae3
epic-harness AGENTS.md is an instructions file published in the GitHub repository epicsagas/epic-harness (18 stars, last pushed 6d ago), licensed Apache-2.0. It adds 4,765 tokens to every session, about $0.0191 per session on Opus 5.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-30.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.