Borrowing it
Nothing to install: this file belongs to exon-research/genomi. 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/exon-research/genomi/master/AGENTS.mdgit clone --depth 1 https://github.com/exon-research/genomiWrote 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/exon-research/genomi/agents-md)<a href="https://agentmods.dev/instructions/exon-research/genomi/agents-md"><img src="https://agentmods.dev/badge/instructions/exon-research/genomi/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/exon-research/genomi/agents-md"><img src="https://agentmods.dev/badge/instructions/exon-research/genomi/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.05815 | $0.05815 |
| Opus 5.5 | $0.02326 | $0.02326 |
| Sonnet 5.5 | $0.01163 | $0.01163 |
| Haiku 4.5 | $0.00581 | $0.00581 |
Grade A, and why
genomi 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 — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Genomi Development Agent Instructions
This file is for agents developing Genomi itself. It is not host-agent runtime
guidance. Host-facing runtime guidance lives in SKILL.md, focused skill docs,
and Genomi MCP tool metadata.
Genomi Design Principles
Edit this section only with explicit owner approval.
-
Genomi should balance deterministic computation with agent judgment. Tools should structure evidence, not become a bottleneck that prevents the agent from using its reasoning.
-
Tool contracts should carry the architecture. Routing and answer-selection rules belong in schemas, required parameters, tool names, and runtime validation, not mainly in skill Markdown.
-
Tool names must be distinct verbs that say what the tool does. If multiple tools share the same real job, refactor or consolidate them. Do not keep aliases or backward-compatible duplicate names.
-
Candidate-gene evidence must preserve source priors. Drug-target, GWAS, screen, rare-disease, and locus-to-gene evidence can point to different candidates. Do not collapse them into one universal "best" gene.
-
Agent decisions need their evidence everywhere. Any tool surface that presents a candidate, ranking, or answer-shaped result must also present the evidence that led to it. The agent host decides.
-
Progressive disclosure should move from capability to focused tools, without mandatory ceremony. Do not expose the whole toolset at once, but do not force bootstrap and repeated discovery before ordinary evidence work.
-
Internal coherence is not enough. A cleaner tool surface can still reduce answer quality if it makes the wrong evidence prior feel authoritative.
-
Agent-facing documents should not expose Genomi internals. They should describe capabilities, privacy boundaries, and how to use tools, not internal implementation details.
-
Agent-facing surfaces must preserve the Active Genome Index boundary. Raw genome sources and parsed Active Genome Index artifacts are session-scoped. Do not expose or reuse them across chats unless the current session explicitly supplies or approves that context.
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 First seen · 518 lines · 5,815 tokens per session scan A 4a3d7f93752d
genomi AGENTS.md is an instructions file published in the GitHub repository exon-research/genomi (489 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 5,815 tokens to every session, about $0.0233 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.
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.
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).