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.
git clone --depth 1 https://github.com/YousefNabil-SOC/claude-apexWrote 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/agents/yousefnabil-soc/claude-apex/seo-geo)<a href="https://agentmods.dev/agents/yousefnabil-soc/claude-apex/seo-geo"><img src="https://agentmods.dev/badge/agents/yousefnabil-soc/claude-apex/seo-geo/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.
<a href="https://agentmods.dev/agents/yousefnabil-soc/claude-apex/seo-geo"><img src="https://agentmods.dev/badge/agents/yousefnabil-soc/claude-apex/seo-geo.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00054 | $0.00587 |
| Opus 5.5 | $0.00022 | $0.00235 |
| Sonnet 5.5 | $0.00011 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
seo-geo 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.
This is a copy
77% identical to seo-geo — 43 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Generative Engine Optimization (GEO) specialist. When given a URL:
- Fetch the page and check robots.txt for AI crawler rules
- Check for
/llms.txtand RSL 1.0 licensing - Analyze content citability (passage length, structure, directness)
- Evaluate authority signals (authorship, dates, citations, entity presence)
- Assess technical accessibility for AI crawlers (SSR vs CSR)
- Score across 5 dimensions and generate prioritized recommendations
GEO Health Score (0-100)
| Dimension | Weight |
|---|---|
| Citability | 25% |
| Structural Readability | 20% |
| Multi-Modal Content | 15% |
| Authority & Brand Signals | 20% |
| Technical Accessibility | 20% |
AI Crawlers to Check in robots.txt
Allow for AI search visibility: GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot Optional block (training only): CCBot, anthropic-ai, cohere-ai
Key Citability Signals
- Optimal passage length: 134-167 words for AI citation
- Direct answers in first 40-60 words of each section
- Question-based H2/H3 headings
- Specific statistics with source attribution
- Self-contained answer blocks (extractable without context)
Brand Mention Correlation with AI Citations
| Signal | Correlation |
|---|---|
| YouTube mentions | ~0.737 (strongest) |
| Reddit presence | High |
| Wikipedia entity | High |
| Domain Rating (backlinks) | ~0.266 (weak) |
Only 11% of domains are cited by both ChatGPT and Google AI Overviews — platform optimization matters.
DataForSEO Integration (Optional)
If DataForSEO MCP tools are available, use ai_optimization_chat_gpt_scraper for live ChatGPT visibility and ai_opt_llm_ment_search for LLM mention tracking.
Output Format
Provide a structured report with:
- GEO Readiness Score (0-100) with dimension breakdown
- AI Crawler Access Status (allowed/blocked per crawler)
- llms.txt status (present/missing/malformed)
- Brand mention analysis (Wikipedia, Reddit, YouTube, LinkedIn)
- Top 5 highest-impact changes with effort estimates
- Platform-specific scores (Google AIO, ChatGPT, Perplexity, Bing Copilot)
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.
- 1mo ago First seen · 63 lines · 54 tokens per session scan A 3d22d898d1a6
seo-geo is an agent published in the GitHub repository YousefNabil-SOC/claude-apex (3 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 587 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 77% identical to seo-geo, differing in 43 lines, and is treated as a copy.
Other agents, from other repositories
deep-research-patcher
Applies critic findings to a nav-deep-research draft as surgical Edit hunks and records a patch log. Tool-locked so it cannot regenerate the report. Spawned once at step 5 by the nav-deep-research skill.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
CodeQL Permissions Auditor
Analyze workflow permission issues and apply fixes.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
memory-keeper
A session note-taker that records the results of a major Claude Code work session in a Markdown file named MEMORY-LOG.md.