Omnigent is an open-source orchestration layer for running and coordinating different AI coding agents through one system. It is for developers who want to combine agents, apply policies and sandboxing, and continue sessions across devices. The catalogue add-ons extend its agent workflows.
Borrowing it
Nothing to install: this file belongs to omnigent-ai/omnigent. 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/omnigent-ai/omnigent/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/omnigent-ai/omnigentWrote 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/omnigent-ai/omnigent/copilot-instructions)<a href="https://agentmods.dev/instructions/omnigent-ai/omnigent/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/omnigent-ai/omnigent/copilot-instructions/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/omnigent-ai/omnigent/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/omnigent-ai/omnigent/copilot-instructions.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.01004 | $0.01004 |
| Opus 5.5 | $0.00402 | $0.00402 |
| Sonnet 5.5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
omnigent 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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Code Review Instructions
E2E Test Requirement
Every pull request that introduces a new feature must include at least one end-to-end (e2e) test covering the happy-path behaviour of that feature. For frontend-only changes, follow Frontend Test Coverage below instead.
- E2E tests live under
tests/e2e/. - If a PR adds new user-facing functionality and does not add or update an e2e test, flag it as a required change.
- Bug-fix or refactor PRs that do not change observable behaviour are exempt.
Backend Test Coverage
A pull request that changes behaviour under omnigent/ should add or update a
test in the suite matching the area it touches. If a behaviour change ships
without a covering test, flag it and name the suite the test belongs in.
Prefer a fast, focused unit test in the area suite — that is what most
changes need. Only expect an integration or e2e test when the change
genuinely spans components or full-stack flows; do not push for a heavier test
where a unit test would suffice.
Most backend areas mirror their source directory under tests/:
Area changed (omnigent/…) |
Expected test suite (tests/…) |
|---|---|
server/ |
server/ |
runner/ |
runner/ |
runtime/ |
runtime/ |
tools/ |
tools/ |
inner/ |
inner/ |
llms/ |
llms/ |
db/ |
db/ (flag schema migrations especially) |
policies/ |
policies/ |
repl/ |
repl/ |
entities/ |
entities/ |
stores/ |
stores/ |
host/ |
host/ |
spec/ |
spec/ |
- A test under
tests/integration/ortests/e2e/that exercises the change also satisfies the requirement — don't insist on the exact area suite. - Do not ask for a test for pure refactors, renames, type-only changes, dependency bumps, comment/docstring/logging edits, or anything with no observable behaviour change.
- A trivial, empty, or unrelated test does not count as coverage.
- When in doubt about whether a change needs a test, raise it as a question rather than a required change.
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.
- 2d ago Changed · +13 lines · +174 tokens per session 98f0132ad8ff
- 29d ago Changed · +4 lines · +42 tokens per session 2170c0b718bf
- 2mo ago First seen · 69 lines · 788 tokens per session scan A 2f854e4e876d
omnigent copilot-instructions.md is an instructions file published in the GitHub repository omnigent-ai/omnigent (11,100 stars, last pushed today), licensed Apache-2.0. It adds 1,004 tokens to every session, about $0.0040 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.