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/archimedes-run/omniharness/copilot-instructionsgit clone --depth 1 https://github.com/archimedes-run/omniHarnessWrote 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/archimedes-run/omniharness/copilot-instructions)<a href="https://agentmods.dev/instructions/archimedes-run/omniharness/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/archimedes-run/omniharness/copilot-instructions.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.01717 | $0.01717 |
| Opus 5 | $0.00859 | $0.00859 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00172 | $0.00172 |
Grade A, and why
omniHarness copilot-instructions.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 5d 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
91% identical to deer-flow copilot-instructions.md — 18 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Onboarding Instructions for OmniHarness
Use this file as the default operating guide for this repository. Follow it first, and only search the codebase when this file is incomplete or incorrect.
1) Repository Summary
OmniHarness is a full-stack "super agent harness".
- Backend: Python 3.12, LangGraph + FastAPI gateway, sandbox/tool system, memory, MCP integration.
- Frontend: Next.js 16 + React 19 + TypeScript + pnpm.
- Local dev entrypoint: root
Makefilestarts backend + frontend + nginx onhttp://localhost:2026. - Docker dev entrypoint:
make docker-*(mode-aware provisioner startup fromconfig.yaml).
Current repo footprint is medium-large (backend service, frontend app, docker stack, skills library, docs).
2) Runtime and Toolchain Requirements
Validated in this repo on macOS:
- Node.js
>=22(validated with Node23.11.0) - pnpm (repo expects lockfile generated by pnpm 10; validated with pnpm
10.26.2and10.15.0) - Python
>=3.12(CI uses3.12) uv(validated with0.7.20)nginx(required formake devunified local endpoint)
Always run from repo root unless a command explicitly says otherwise.
3) Build/Test/Lint/Run - Verified Command Sequences
These were executed and validated in this repository.
A. Bootstrap and install
- Check prerequisites:
make check
Observed: passes when required tools are installed.
- Install dependencies (recommended order: backend then frontend, as implemented by
make install):
make install
B. Backend CI-equivalent validation
Run from backend/:
make lint
make test
Validated results:
make lint: pass (ruff check .)make test: pass (277 passed, 15 warnings in ~76.6s)
CI parity:
.github/workflows/backend-unit-tests.ymlruns on pull requests.- CI executes
uv sync --group dev, thenmake lint, thenmake testinbackend/.
C. Frontend validation
Run from frontend/.
Recommended reliable sequence:
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.
- 5d ago First seen · 214 lines · 1,717 tokens per session scan A faef5d6ad9d3
omniHarness copilot-instructions.md is an instructions file published in the GitHub repository archimedes-run/omniHarness (7 stars, last pushed 10d ago), licensed MIT. It adds 1,717 tokens to every session, about $0.0086 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to deer-flow copilot-instructions.md, differing in 18 lines, and is treated as a copy.
Other instructions, from other repositories
appwrite AGENTS.md
AGENTS.md instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
meme-search CLAUDE.md
Instructions for neonwatty/meme-search, covering claude.md, 📁 file organization guidelines, 🤖 task agent usage guidelines, when to use task agents and documentation lookup pattern.
selfhost-ai CLAUDE.md
Claude Code instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
SForum AGENTS.md
AGENTS.md instructions for zhuchunshu/SForum, covering agent guide, project intent, working principles, stack and directory map and commands.
redd-archiver CLAUDE.md
Instructions for 19-84/redd-archiver, covering claude.md, project overview, deviations from global standards, build & run commands and docker development (primary method).
homelab-monitor CLAUDE.md
Claude Code instructions for SikamikanikoBG/homelab-monitor, covering claude.md and conventions.