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/every-app/open-seo/agents-mdgit clone --depth 1 https://github.com/every-app/open-seoWhat 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.00493 | $0.00493 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
open-seo 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 3d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- upgradeseo AGENTS.md — 100% identical, 0 lines differ
- open-seo CLAUDE.md — 86% identical, 12 lines differ
- upgradeseo CLAUDE.md — 86% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent guidance
Engineering principles
- Prefer simple, readable, flat code with minimal indirection.
- Search for existing implementations and installed libraries before creating new helpers or abstractions.
- Abstract when it prevents meaningful drift and makes the result simpler to maintain. Avoid speculative or one-use abstraction layers.
- Keep product data normalized and relationships explicit. Do not encode relational data in JSON or text merely to avoid joins.
- For new application-backed backend functionality, default to: TanStack server function → service → repository.
- Keep schema changes, queries, and mutations compatible with both SQLite and Postgres.
- Use idiomatic TypeScript. Use Zod to validate untrusted data and narrow runtime values at trust boundaries.
- Prefer established project helpers and libraries over hand-rolled implementations.
- Prefer idiomatic TanStack Query, Router, and Form patterns for server state, routing, and submitted forms.
Log papercuts
When small, non-blocking repository friction occurs—a retried tool call, confusing setup step, flaky command, stale cache, misleading error, or non-obvious gotcha—use the papercuts skill and append it to .agents/PAPERCUTS.md in the moment. Continue the current task. Real bugs and tracked work are not papercuts, and sensitive data must never be logged.
Do not mine an entire session for papercuts or start a broad cleanup unless the user explicitly asks.
Preserve review learnings
After a merge-ready or other code review verifies a finding, use maintain-greptile-rules only when the finding exposes a recurring or high-risk repository invariant that existing .greptile/ context and automated checks do not capture. Do not promote one-off bugs or preferences into permanent review rules.
Changes to .greptile/**, AGENTS.md, CLAUDE.md, .agents/skills/**, and .github/** alter the review control plane and must receive explicit maintainer review. CODEOWNERS requests that review; where repository settings allow, enable GitHub's requirement for code-owner approval. Repository-specific rules live in .greptile/; maintainers should configure or retain a minimal org-enforced Greptile baseline for external-contribution, secret, authentication, billing, CI, and rule-tampering risks. Agents should report an unverified or missing baseline and must not mutate dashboard or organization rules without explicit user authorization.
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.
- 3d ago First seen · 26 lines · 493 tokens per session scan A ceb5aebad460
open-seo AGENTS.md is an instructions file published in the GitHub repository every-app/open-seo (16,131 stars, last pushed 10d ago), licensed MIT. It adds 493 tokens to every session, about $0.0025 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
yandex-wordstat-guide AGENTS.md
Instructions for axelfreeman/yandex-wordstat-guide, covering agents.md — yandex wordstat guide for ai agents, what this project is, quick start for ai agents, prerequisites and 1. clone.
svelte-vitals AGENTS.md
Instructions for oekazuma/svelte-vitals, covering agents.md, what this is, verify commands, package map and hard rules.
svelte-vitals CLAUDE.md
Instructions for oekazuma/svelte-vitals: See @AGENTS.md for repository conventions, verify commands, and hard rules.
dataseo-mcp AGENTS.md
AGENTS.md instructions for egebese/dataseo-mcp, covering agents.md, product, public tool contracts, architecture rules and development commands.
dataseo-mcp CLAUDE.md
Claude Code instructions for egebese/dataseo-mcp, covering claude.md, use, tools, environment and development notes.
kwrds-ai-mcp CLAUDE.md
Instructions for mkotsollaris/kwrds-ai-mcp, covering claude.md, project overview, development commands, setup and run the server (for testing).