seoagent: Instructions file for Codex

AGENTS.md

seoagent AGENTS.md is an instructions file for Codex, OpenCode from yagomp/seoagent. It costs 1,018 tokens per session, scanned A, original, MIT.

Repository instructions for SEOAgent, a codebase for search-engine-optimization work, covering its packages, feature workflow, and testing patterns.

In plain words
What is it for?
Use them when adding or testing SEOAgent features across its core package, CLI, MCP server, or dashboard.
Why use it?
They show where business logic, types, tests, command-line commands, MCP tools, and dashboard code belong, so changes fit the project structure.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions Codex.

This is yagomp/seoagent's own configuration. It tells Codex and OpenCode how to work on seoagent 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 seoagent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to yagomp/seoagent. 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/yagomp/seoagent/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/yagomp/seoagent

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 seoagent AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yagomp/seoagent/agents-md/github.svg)](https://agentmods.dev/instructions/yagomp/seoagent/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/yagomp/seoagent/agents-md"><img src="https://agentmods.dev/badge/instructions/yagomp/seoagent/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 seoagent AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/yagomp/seoagent/agents-md"><img src="https://agentmods.dev/badge/instructions/yagomp/seoagent/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,018 This file is loaded in full into every session.
When invoked 1,018 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.01018 $0.01018
Opus 5.5 $0.00407 $0.00407
Sonnet 5.5 $0.00204 $0.00204
Haiku 4.5 $0.00102 $0.00102

Measured 1mo ago against content hash 95d4841f78af, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SEOAgent — Agent Instructions

This file provides instructions for AI coding agents (Claude Code, Codex, Gemini, Cursor, etc.) working on the SEOAgent codebase.

Quick Start

pnpm install && pnpm build && pnpm test

Where Things Live

What Where
All business logic packages/core/src/
Public API packages/core/src/index.ts (barrel export)
Types packages/core/src/types.ts
Database schema packages/core/src/schema.ts
Tests packages/core/src/__tests__/*.test.ts
CLI commands packages/cli/src/commands/
MCP tool handlers packages/mcp/src/tools/
Dashboard API packages/dashboard/src/server/routes.ts
Dashboard pages packages/dashboard/src/app/pages/

Adding a New Feature

  1. Add types to packages/core/src/types.ts (if needed)
  2. Write failing test in packages/core/src/__tests__/
  3. Implement in packages/core/src/ (new file or existing module)
  4. Export from packages/core/src/index.ts
  5. Add CLI command in packages/cli/src/commands/
  6. Add MCP tool in packages/mcp/src/tools/
  7. Add dashboard endpoint + page if applicable

Testing Patterns

  • Mock HTTP calls with vitest.mock("undici") or vitest.mock("googleapis")
  • Mock DataForSEO with vitest.mock("../dataforseo.js")
  • Use SEOAGENT_HOME env var pointing to temp dir for isolated tests
  • Database tests: create temp dir, openDatabase(), cleanup in afterEach
let tmpDir: string;
beforeEach(() => {
  tmpDir = fs.mkdtempSync(path.join(os.tmpdir(), "seoagent-test-"));
  process.env.SEOAGENT_HOME = tmpDir;
});
afterEach(() => {
  fs.rmSync(tmpDir, { recursive: true, force: true });
});

MCP Server

24 tools prefixed seoagent_. Install config:

{
  "mcpServers": {
    "seoagent": {
      "command": "node",
      "args": ["<absolute-path>/packages/mcp/dist/index.js"],
      "env": { "SEOAGENT_PROJECT": "<project-slug>" }
    }
  }
}

CLI

seoagent project add mysite --domain example.com --niche tech
seoagent project use mysite
seoagent config set dataforseo.login <login>
seoagent config set dataforseo.password <password>
seoagent keywords research "seo tips" --format json
seoagent audit crawl --max-pages 100
seoagent strategy generate

Read the full file on GitHub · 115 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. 1mo ago First seen · 115 lines · 1,018 tokens per session scan A 95d4841f78af

Subscribe to this mod's changes

seoagent AGENTS.md is an instructions file published in the GitHub repository yagomp/seoagent (0 stars, last pushed 6mo ago), licensed MIT. It adds 1,018 tokens to every session, about $0.0041 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-31.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens