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/mverab/egeoagents/agents-mdgit clone --depth 1 https://github.com/mverab/eGEOagentsWrote 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/mverab/egeoagents/agents-md)<a href="https://agentmods.dev/instructions/mverab/egeoagents/agents-md"><img src="https://agentmods.dev/badge/instructions/mverab/egeoagents/agents-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.00919 | $0.00919 |
| Opus 5 | $0.00460 | $0.00460 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
eGEOagents 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 4d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Instructions
These instructions are for AI assistants working in this project.
Always open @/openspec/AGENTS.md when the request:
- Mentions planning or proposals (words like proposal, spec, change, plan)
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
- Sounds ambiguous and you need the authoritative spec before coding
Use @/openspec/AGENTS.md to learn:
- How to create and apply change proposals
- Spec format and conventions
- Project structure and guidelines
Keep this managed block so 'openspec update' can refresh the instructions.
AGENTS.md
Project: E-GEO (Generative Engine Optimization)
A zero-effort system to optimize website content for AI-powered search engines (ChatGPT, Perplexity, Claude, Gemini).
Quick Start
/geo https://yoursite.com/page
That's it. The system handles everything automatically.
Available Commands
| Command | Description |
|---|---|
/geo <url> |
Full optimization pipeline |
/geo:audit <url> |
Analysis only |
/geo:optimize <file> |
Optimize local file |
/geo:batch <folder> |
Process multiple files |
/geo:report |
Generate summary report |
/geo:compete <query> |
Competitive analysis |
Code Style
- Markdown for all content files
- JSON-LD for schema markup
- YAML frontmatter for metadata
MCP Requirements
For fully validated results (ground truth competitors + rendered DOM), use these MCP servers. If they're missing, the system should still run but must mark outputs as Low Confidence.
| Server | Purpose | Criticality |
|---|---|---|
brave-search |
Market validation (competitor analysis) | 🔴 HIGH |
chrome-devtools |
Technical validation (DOM/rendering) | 🔴 HIGH |
Use the validation-doctor skill to check or install these dependencies.
Agent Instructions
When Optimizing Content
- VALIDATE ALWAYS: Use
brave-searchfor competitor ground truth andchrome-devtoolsfor rendered DOM when available.- If missing, validate with available tools (e.g.,
fetch/raw HTML) and clearly label outputs as Low Confidence. - Do not claim competitor rankings without Brave data.
- If missing, validate with available tools (e.g.,
- Always analyze before rewriting
- Preserve brand voice and factual accuracy
- Apply the 10 GEO universal features
- Generate schema markup for all pages
- Provide before/after comparison
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.
- 4d ago First seen · 130 lines · 919 tokens per session scan A e83f1cb60f8e
eGEOagents AGENTS.md is an instructions file published in the GitHub repository mverab/eGEOagents (172 stars, last pushed 2d ago), licensed MIT. It adds 919 tokens to every session, about $0.0046 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-30.
Other instructions, from other repositories
claude-rank CLAUDE.md
Instructions for Houseofmvps/claude-rank, covering claude-rank, project overview, architecture, tech stack and conventions.
notion-geo-audit CLAUDE.md
Claude Code instructions for nycsav/notion-geo-audit, covering notion-geo-audit — project guide, what this is, live surfaces (all launched, public), architecture and build / deploy.
aeo-radar CLAUDE.md
Instructions for hellowalt/aeo-radar, covering claude.md — dev playbook for aeo radar, tech stack, common commands, crawl (defaults to headless) and seeding & analysis.
seohead-seotools AGENTS.md
AGENTS.md instructions for PavloSEO/seohead-seotools, covering agents.md — public repository contract, product model, start here, architecture and invariants.
seo-geo-optimizer copilot-instructions.md
Instructions for Aryanpanwar10005/seo-geo-optimizer, covering seo & geo optimizer — universal ai skill, how to use this skill, part 1 — iron laws, part 2 — seo & geo execution phases and phase 0 — initialize.
aitraffic AGENTS.md
AGENTS.md instructions for devanshug2307/aitraffic, covering agents.md, purpose, canonical commands, terminal contract and evidence contract.