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/getomnico/omni/agents-mdgit clone --depth 1 https://github.com/getomnico/omniWrote 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/getomnico/omni/agents-md)<a href="https://agentmods.dev/instructions/getomnico/omni/agents-md"><img src="https://agentmods.dev/badge/instructions/getomnico/omni/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.02052 | $0.02052 |
| Opus 5 | $0.01026 | $0.01026 |
| Sonnet 5 | $0.00410 | $0.00410 |
| Haiku 4.5 | $0.00205 | $0.00205 |
Grade A, and why
omni 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 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Omni
Omni is an open-source, self-hosted AI agent for the workplace. It connects to the apps a team already uses (Google Drive, Gmail, Slack, Confluence, etc.), syncs their data into a unified BM25 and pgvector index, and provides an agent harness that can search, reason over, and act on that data using any major cloud or private (self-hosted) model provider.
Core Philosophy
The core philosophy behind the project is simplicity: use Postgres (ParadeDB) as the primary application storage system and hybrid (text + vector) search index, minimizing operational complexity.
Features
- Built-in connectors that sync workplace app data through source-appropriate polling or webhook mechanisms (Google Drive, Gmail, Slack, Confluence, Jira, and many more), with one container per connector
- Each connector can sync data across multiple related apps. E.g., the google connector syncs data from Drive, Gmail and Chat.
- An agent harness (omni-ai) that orchestrates LLM agents with tools for index search, file download, bash/python execution, and more, including auto-compaction, context management and memory
- A unified index (BM25 + pgvector) over all connected sources, with a search UI and LLM summarization of results
- Model flexibility: works with all major cloud LLM providers (OpenAI, Anthropic, Gemini, AWS Bedrock, etc.) as well as private/self-hosted models, plus pluggable embedding providers (Jina AI, Cohere, OpenAI, etc.)
- A web-based chat UI for interacting with the agent.
Architecture
Omni's main application services run as separate containers, alongside one container per connector.
Why one container per connector? To allow developers full control over packaging their dependencies without affecting other connectors.
Core Services & Code Organization
- All core services are under services/ and web/ a. omni-searcher (services/searcher): handles all index search requests b. omni-indexer (services/indexer): handles all writes to the index c. omni-ai (services/ai): orchestrates all LLM interactions, agents d. omni-web (web/): frontend SvelteKit app e. omni-connector-manager (services/connector-manager): orchestrates all connector containers f. omni-sandbox (services/sandbox): Sandbox container for bash and python execution, file manipulation
- One container per connector, built-in connectors are in connectors/ a. omni-google-connector (drive & gmail) b. omni-slack-connector c. omni-atlassian-connector (confluence & jira), and so on
- Connector SDKs in Python, TypeScript and Rust under sdk/
- Database migrations: services/migrations.
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 First seen · 125 lines · 2,052 tokens per session scan A 7e7accb3a0db
omni AGENTS.md is an instructions file published in the GitHub repository getomnico/omni (771 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,052 tokens to every session, about $0.0103 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-09-03.
Other instructions, from other repositories
GPT-RAG release.instructions.md
Instructions for Azure/GPT-RAG, a project described as: Enterprise-grade accelerator for agentic RAG on Azure. Built on Microsoft Foundry with Foundry IQ as the default retrieval backend, Microsoft Agent Framework orchestration, Zero-Trust architecture and IaC.
gpt-rag-ingestion api-frontend.instructions.md
Instructions for Azure/gpt-rag-ingestion, a project described as: The GPT-RAG Data Ingestion service automates processing of diverse documents—PDFs, images, spreadsheets, transcripts, and SharePoint—readying them for Azure AI Search. It applies smart chunking, generates text and image embeddings, and enables rich…
RAGElo copilot-instructions.md
Instructions for zetaalphavector/RAGElo, covering copilot instructions — ragelo, project overview, commands, install for development and run with openai integration tests (requires openaiapikey).
pdf-brain AGENTS.md
Instructions for joelhooks/pdf-brain, covering pdf-brain agent notes, libsql quirks, ai sdk pattern, key files and docs.
rag-code-mcp copilot-instructions.md
Instructions for doITmagic/rag-code-mcp, covering copilot instructions - ragcode mcp, ⚖️ the golden rule, project overview, architecture & patterns and developer workflows.
autonomous-rag CLAUDE.md
Claude Code instructions for BhavyaFattania/autonomous-rag, covering claude code configuration, rules, knowledge graph navigation (graphify-out/), design principles (derived from codebase audit) and build & test.