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/yagomp/seoagent/claude-mdgit clone --depth 1 https://github.com/yagomp/seoagentWrote 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/yagomp/seoagent/claude-md)<a href="https://agentmods.dev/instructions/yagomp/seoagent/claude-md"><img src="https://agentmods.dev/badge/instructions/yagomp/seoagent/claude-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 | $0.00593 | $0.00593 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
seoagent CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEOAgent
Open-source, agent-first SEO toolkit — keyword research, rank tracking, site audits, competitor analysis, content gap analysis, domain reputation, and AI-powered strategy generation.
Architecture
TypeScript pnpm monorepo with 4 packages:
packages/core/(@seoagent/core) — all business logic. Every feature is a function here first.packages/cli/(seoagent) — commander.js CLI, thin wrapper over corepackages/mcp/(seoagent-mcp) — MCP server with 24 tools, thin wrapper over corepackages/dashboard/— Vite + React + Tailwind local web UI (read-only)
Tech Stack
- TypeScript, Node.js >= 20, pnpm workspaces
- SQLite via better-sqlite3 (one DB per project at
~/.seoagent/projects/<slug>/seoagent.db) - Vitest for testing (260 tests across 38 files)
- DataForSEO for keyword/SERP/backlink data
- Google Search Console API (googleapis)
- LLM strategy: Anthropic SDK, OpenAI SDK, Ollama (fetch)
- Crawler: undici + cheerio
- Dashboard: Vite, React, React Router, Tailwind CSS v4, Recharts
Key Commands
pnpm install # install all deps
pnpm build # build all packages
pnpm test # run all tests
pnpm -r run test # run tests across all packages
# Core only
cd packages/core && pnpm test
cd packages/core && pnpm build
Code Conventions
- All business logic in
packages/core/src/. CLI/MCP/Dashboard are thin wrappers. - Barrel export from
packages/core/src/index.ts— add new exports there. - Tests in
packages/core/src/__tests__/using Vitest with globals. - TDD workflow: test first, implement, verify.
- SQLite schema in
packages/core/src/schema.ts— tables created viaopenDatabase(). - Config at
~/.seoagent/config.json, projects at~/.seoagent/projects/<slug>/. SEOAGENT_HOMEenv var overrides~/.seoagent(used in tests with temp dirs).
Data Sources
- Free: Google Search Console API, PageSpeed Insights, local crawler
- Paid: DataForSEO (~$0.001/query) — keyword volumes, SERP, backlinks
- Derived: content gaps, rank deltas, audit scores, strategy (LLM or rule-based)
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 · 57 lines · 593 tokens per session scan A f9df59746a41
seoagent CLAUDE.md is an instructions file published in the GitHub repository yagomp/seoagent (0 stars, last pushed 5mo ago), licensed MIT. It adds 593 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
social-media-research-skills AGENTS.md
AGENTS.md instructions for ScrapeCreators/social-media-research-skills, covering social media research skills repo, authoring guidelines and validation.
social-media-research-skills CLAUDE.md
Claude Code instructions for ScrapeCreators/social-media-research-skills: Use these skills as practical social media research workflows.
crawlseo AGENTS.md
Instructions for crawlseo/crawlseo, a project described as: Open-source SEO monitoring. GSC + Site Crawler + Core Web Vitals in one dashboard.
app-store-operator CLAUDE.md
Instructions for meyusufdemirci/app-store-operator, covering app store operator — mcp server, codebase, server wiring, tool module contract and prompts.
backlink-pilot CLAUDE.md
Instructions for s87343472/backlink-pilot, covering backlink pilot v2.1 — claude code instructions, first-time user flow, step 1: check prerequisites, step 2: create config.yaml and step 3: start chrome.
seo-survival-kit CLAUDE.md
Instructions for maxschottke-spec/seo-survival-kit, covering seo-survival-kit: project instructions for claude code, what this repository is, architecture, routing and skill-naming convention.