open-seo: Instructions file for Codex

AGENTS.md

open-seo AGENTS.md is an instructions file for Codex, OpenCode from every-app/open-seo. It costs 1,926 tokens per session, scanned A, original, MIT.

Repository instructions for developing OpenSEO, a search-engine-optimisation application. They describe coding practices, data handling, database compatibility, and how to record small development problems.

In plain words
What is it for?
Guiding changes to the TypeScript application, server functions, database code, forms, routing, and project notes about development friction.
Why use it?
They give the coding agent consistent project rules and help prevent avoidable maintenance and database mistakes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions .claude-plugin; mentions CLAUDE.md; mentions AGENTS.md.

This is every-app/open-seo's own configuration. It tells Codex and OpenCode how to work on open-seo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything open-seo configures →

About the project

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.

every-app/open-seo · 25,345 stars · on GitHub · openseo.so

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/every-app/open-seo/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/every-app/open-seo

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for open-seo AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/every-app/open-seo/agents-md/github.svg)](https://agentmods.dev/instructions/every-app/open-seo/agents-md)
Your own site
<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.

agentmods 80×15 button for open-seo AGENTS.md

Your own site · 80×15
<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>
Per session 1,926 This file is loaded in full into every session.
When invoked 1,926 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash ec6b2cfaef2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

AGENTS.md · 70 lines

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 the render prop, not asChild.
  • 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 create copies 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-seo from an Every App checkout (the npm CLI installed here cannot deploy). Never run cf deploy or wrangler deploy for this mode. deploy:selfhost is the other self-hosting path (pnpm deploy is the plain wrangler deploy of wrangler.jsonc) and deploy:postgres is 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 and why) in everyapp.config.ts; cloudflare.config.ts builds 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 under public in everyapp.config.ts as open to the internet.

Read the full file on GitHub · 70 lines

Changes

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.

  1. yesterday Changed · +10 lines · +370 tokens per session ec6b2cfaef2a
  2. 13d ago Changed · +1 lines · +57 tokens per session 20e4a9668e6c
  3. 19d ago Changed · +1 lines · +66 tokens per session 2f99b4254bd1
  4. 27d ago Changed · +25 lines · +789 tokens per session 5fcd23a6e8e8
  5. 1mo ago Changed · +7 lines · +151 tokens per session 508243f102e5
  6. 1mo ago First seen · 26 lines · 493 tokens per session scan A ceb5aebad460

Subscribe to this mod's changes

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.

Related

Other instructions, from other repositories