OpenSEO is an open-source SEO platform for keyword research, rank tracking, competitor analysis, backlink analysis, site audits, and AI visibility work. It connects SEO data to AI agents through an MCP server and reusable agent skills, while allowing users to supply their own DataForSEO API key and self-host the tool. Catalogue add-ons guide agents through OpenSEO's SEO workflows.
Borrowing it
Nothing to install: this file belongs to every-app/open-seo. 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/every-app/open-seo/main/AGENTS.mdgit clone --depth 1 https://github.com/every-app/open-seoWrote 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/every-app/open-seo/agents-md)<a href="https://agentmods.dev/instructions/every-app/open-seo/agents-md"><img src="https://agentmods.dev/badge/instructions/every-app/open-seo/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/every-app/open-seo/agents-md"><img src="https://agentmods.dev/badge/instructions/every-app/open-seo/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.01926 | $0.01926 |
| Opus 5.5 | $0.00770 | $0.00770 |
| Sonnet 5.5 | $0.00385 | $0.00385 |
| Haiku 4.5 | $0.00193 | $0.00193 |
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 yesterday.
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
2 near-identical copies found in the catalogue:
- upgradeseo AGENTS.md — 100% identical, 48 lines differ
- upgradeseo CLAUDE.md — 86% identical, 36 lines differ
How it starts
The opening of the file, as written. The whole thing — 70 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.
- Work on bugs a real user hit or would plausibly hit. Don't open a ticket or PR for an edge case found only by reading the code; flag it instead. Security holes and significant billing abuse are the exception.
- 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.
- shadcn components in
src/client/components/ui/are built on Base UI, not Radix. Compose them with therenderprop, notasChild. - Specs under
docs/maintainers/specs/are public design records: what a feature does, how it works, the alternatives considered and why they lost. No line numbers, migration mechanics, test plans, incidents, costs, or internal infrastructure details.
Every App
OpenSEO also runs behind an Every App Gateway (AUTH_MODE=everyapp; how it works is in docs/maintainers/every-app.md).
- Before running everyapp, read the everyapp skill. It lives in the platform checkout beside this repository,
../private-every-app/packages/cli/skills/everyapp/SKILL.md;everyapp createcopies it into new apps, and this port reads it from there. - Run the app with
pnpm dev:everyapp(everyapp dev): both Workers behind a local gateway with a seeded dev user. The keys it needs locally go in.dev.vars, written by hand. - Deploy only through the Every App CLI:
pnpm everyapp install https://github.com/every-app/open-seofrom an Every App checkout (the npm CLI installed here cannot deploy). Never runcf deployorwrangler deployfor this mode.deploy:selfhostis the other self-hosting path (pnpm deployis the plainwrangler deployofwrangler.jsonc) anddeploy:postgresis app.openseo.so's production deploy; none of them is this one. - Declare resources (D1, KV, Durable Objects, Workflows, the audit Worker) and settings (
providers,capabilities,secrets, each with its need andwhy) ineveryapp.config.ts;cloudflare.config.tsbuilds the Workers from it. - The Gateway signs people in: read identity only through the SDK (
src/middleware/ensure-user/everyApp.ts), never from a client-supplied header or cookie, and treat every route listed underpublicineveryapp.config.tsas open to the internet.
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.
- yesterday Changed · +10 lines · +370 tokens per session ec6b2cfaef2a
- 13d ago Changed · +1 lines · +57 tokens per session 20e4a9668e6c
- 19d ago Changed · +1 lines · +66 tokens per session 2f99b4254bd1
- 27d ago Changed · +25 lines · +789 tokens per session 5fcd23a6e8e8
- 1mo ago Changed · +7 lines · +151 tokens per session 508243f102e5
- 1mo 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 (25,345 stars, last pushed yesterday), licensed MIT. It adds 1,926 tokens to every session, about $0.0077 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.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.