What is seohead-seotools AGENTS.md?

A set of project instructions for SEOHEAD Tools, a local command-line and local agent-server toolkit that checks website data and builds audit reports.

It helps agents work safely on the SEOHEAD codebase, use Screaming Frog exports correctly, preserve failed or skipped checks, and produce audit, task, and report files.

It gives coding agents the repository’s rules, architecture, and limits so they do not add unsupported interfaces or treat the tool as a website crawler.

How PavloSEO/seohead-seotools configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to PavloSEO/seohead-seotools. 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/PavloSEO/seohead-seotools/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/PavloSEO/seohead-seotools

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/pavloseo/seohead-seotools/agents-md/github.svg)](https://agentmods.dev/instructions/pavloseo/seohead-seotools/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/pavloseo/seohead-seotools/agents-md"><img src="https://agentmods.dev/badge/instructions/pavloseo/seohead-seotools/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/pavloseo/seohead-seotools/agents-md"><img src="https://agentmods.dev/badge/instructions/pavloseo/seohead-seotools/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,022 This file is loaded in full into every session.

When invoked 1,022 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.

Model	Per session	Once invoked
Fable 5.1	$0.01022	$0.01022
Opus 5.5	$0.00409	$0.00409
Sonnet 5.5	$0.00204	$0.00204
Haiku 4.5	$0.00102	$0.00102

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

Security

Grade A, and why

seohead-seotools 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 2mo 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 · 93 lines

How it starts

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

AGENTS.md — public repository contract

SEOHEAD Tools is a headless, local-first evidence and audit-automation layer for SEO specialists and tool-calling agents. It has exactly two user interfaces: the seohead CLI and one local stdio MCP server. Do not add a GUI, desktop shell, hosted API, or remote MCP endpoint to this repository.

Product model

Do not present SEOHEAD as a replacement for Screaming Frog or as a collection of unrelated scripts. The crawler and this toolkit have different jobs:

Screaming Frog produces the CSV/XLSX exports consumed by SEOHEAD's 96-check analyzer. Do not imply that another crawler's exports are drop-in compatible.
SEOHEAD analyzes those SF exports, adds bounded live and infrastructure evidence, preserves skipped/failed measurements, and produces structured audit, task, and report artifacts.
The CLI and MCP expose the same tested core so either a specialist or an AI agent can run the workflow without improvising its own crawler.
Skills guide orchestration and interpretation; they are not evidence sources, and final judgement remains with the specialist.

Live SF mode launches a separately installed, actively licensed Screaming Frog CLI. Export mode works from existing CSV/XLSX files. The site-audit command is a bounded sitemap-based pass, not an exhaustive run of the tool catalog and not a general-purpose crawl.

Start here

python -m pip install -e ".[dev,mcp,cluster,reports]"
ruff check .
ruff format --check .
pytest -q
seohead sf run --exports-dir examples/exports --out /tmp/seohead-report --tasks

Architecture

seohead/
  cli.py          CLI registration and argument mapping
  tools/          live page, content, image, log, and structured-data tools
  recon/          domain and infrastructure reconnaissance
  sf/             Screaming Frog export runner and 96-check analyzer
  audit/          bounded sitemap-based evidence orchestration
  reports/        XLSX, DOCX, CSV, Markdown, and JSON formatting
  data_sources/   optional demand, SERP, and traffic providers
  servers/        shared handlers and MCP registration
  skills/         packaged SEO workflow playbooks

Read the full file on GitHub · 93 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.

2mo ago First seen · 93 lines · 1,022 tokens per session scan A e921b1f6bcb1

Subscribe to this mod's changes

seohead-seotools AGENTS.md is an instructions file published in the GitHub repository PavloSEO/seohead-seotools (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,022 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.

Marketing and SEO aeo ai-agents docker geo local-first mcp

seohead-seotools AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
seohead-seotools AGENTS.mdPavloSEO/seohead-seotools	Instructions file	0	2mo ago	MIT	A	1,022	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

seohead-seotools: Instructions file for Codex