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/opencowai/opencow/gemini-mdgit clone --depth 1 https://github.com/OpenCowAI/opencowWrote 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/opencowai/opencow/gemini-md)<a href="https://agentmods.dev/instructions/opencowai/opencow/gemini-md"><img src="https://agentmods.dev/badge/instructions/opencowai/opencow/gemini-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.00422 | $0.00422 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
opencow GEMINI.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 6d 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
100% identical to opencow AGENTS.md — 0 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.
What it actually says
MCP Tools: code-review-graph
IMPORTANT: This project has a knowledge graph. ALWAYS use the code-review-graph MCP tools BEFORE using Grep/Glob/Read to explore the codebase. The graph is faster, cheaper (fewer tokens), and gives you structural context (callers, dependents, test coverage) that file scanning cannot.
When to use graph tools FIRST
- Exploring code:
semantic_search_nodesorquery_graphinstead of Grep - Understanding impact:
get_impact_radiusinstead of manually tracing imports - Code review:
detect_changes+get_review_contextinstead of reading entire files - Finding relationships:
query_graphwith callers_of/callees_of/imports_of/tests_for - Architecture questions:
get_architecture_overview+list_communities
Fall back to Grep/Glob/Read only when the graph doesn't cover what you need.
Key Tools
| Tool | Use when |
|---|---|
detect_changes |
Reviewing code changes — gives risk-scored analysis |
get_review_context |
Need source snippets for review — token-efficient |
get_impact_radius |
Understanding blast radius of a change |
get_affected_flows |
Finding which execution paths are impacted |
query_graph |
Tracing callers, callees, imports, tests, dependencies |
semantic_search_nodes |
Finding functions/classes by name or keyword |
get_architecture_overview |
Understanding high-level codebase structure |
refactor_tool |
Planning renames, finding dead code |
Workflow
- The graph auto-updates on file changes (via hooks).
- Use
detect_changesfor code review. - Use
get_affected_flowsto understand impact. - Use
query_graphpattern="tests_for" to check coverage.
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.
- 6d ago First seen · 39 lines · 422 tokens per session scan A a506e967214a
opencow GEMINI.md is an instructions file published in the GitHub repository OpenCowAI/opencow (396 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 422 tokens to every session, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to opencow AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
claude_code_vs CLAUDE.md
Claude Code instructions for firish/claude_code_vs, covering claude.md, what this is, working agreement (how we collaborate here), architecture (where things live) and tech stack & hard constraints.
Meterless AGENTS.md
Instructions for Meterless/Meterless, covering agent instructions for meterless, routing table, isolation rule, repo-wide rules and non-coding agents.
open-press CLAUDE.md
Instructions for quan0715/open-press, covering claude.md, repo identity, commands, tests and node:test — tests/.test.mjs (engine, cli, export pipeline).
open-press AGENTS.md
Instructions for quan0715/open-press, covering open-press framework — agent contract, what you may edit, what you may not edit, commit message prefixes and branch ownership.
Operator-Use CLAUDE.md
Instructions for Jeomon/Operator-Use, covering operator — claude.md, project overview, repository layout, quick navigation and key invariants.
browser-agent CLAUDE.md
Instructions for uiuing/browser-agent, a project described as: An open-source AI agent for the browser. Bring any model. It plans in the side panel, acts on real pages through tools, and verifies every claimed result against the live DOM — with guardrails and reusable skills.