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/omnigent-ai/omnigent/copilot-instructionsgit 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.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.00788 | $0.00788 |
| Opus 5 | $0.00394 | $0.00394 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 69 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.
- 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.
Frontend Test Coverage
A pull request that changes behaviour under web/ should add or update a
colocated Vitest unit test — a *.test.ts or *.test.tsx file beside the
component or module it touches. If a behaviour change ships without one, flag it.
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 · 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 (9,658 stars, last pushed today), licensed Apache-2.0. It adds 788 tokens to every session, about $0.0039 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-30.
Other instructions, from other repositories
swiftide AGENTS.md
AGENTS.md instructions for bosun-ai/swiftide, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
terminator CLAUDE.md
Instructions for mediar-ai/terminator, covering terminator - ai-native gui automation, installation, release, or with globally installed cli and development.
ai-dial-core CLAUDE.md
Claude Code instructions for epam/ai-dial-core, covering claude.md, build & run, set credentials via environment variables, build (skip tests) and run all tests.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.