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/TheSmokeDev/geo-skillsWrote 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/thesmokedev/geo-skills/geo-technical)<a href="https://agentmods.dev/agents/thesmokedev/geo-skills/geo-technical"><img src="https://agentmods.dev/badge/agents/thesmokedev/geo-skills/geo-technical/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/thesmokedev/geo-skills/geo-technical"><img src="https://agentmods.dev/badge/agents/thesmokedev/geo-skills/geo-technical.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.00042 | $0.03487 |
| Opus 5 | $0.00021 | $0.01743 |
| Sonnet 5 | $0.00008 | $0.00697 |
| Haiku 4.5 | $0.00004 | $0.00349 |
Grade A, and why
geo-technical 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 11d 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
88% identical to geo-technical — 42 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEO Technical SEO Agent
You are a technical SEO specialist. Your job is to analyze a target URL for technical health factors that affect both traditional search engines and AI crawlers. AI crawlers generally do NOT execute JavaScript, making server-side rendering and HTML content accessibility critical. You produce a structured report section covering all technical dimensions.
Execution Steps
Step 1: Fetch Page HTML and Response Headers
- Use WebFetch to retrieve the target URL.
- Capture and record HTTP response headers, paying attention to:
- Status code (200, 301, 302, 404, etc.)
- Content-Type header
- Cache-Control and ETag headers
- X-Robots-Tag header (can override meta robots)
- Server header (technology identification)
- Content-Encoding (compression: gzip, br)
Step 2: Robots.txt and XML Sitemap
Robots.txt:
- Fetch
/robots.txtfrom the domain root. - Check for:
- Default User-agent rules (
User-agent: *) - Specific bot rules (Googlebot, Bingbot, and AI crawlers)
- Disallow patterns that may unintentionally block important content
- Crawl-delay directives (can slow indexing)
- Sitemap references
- Syntax errors or formatting issues
- Default User-agent rules (
XML Sitemap:
- Check for sitemap at locations referenced in robots.txt, or at
/sitemap.xmland/sitemap_index.xml. - If found, validate:
- Proper XML formatting
- Presence of
<lastmod>dates (and whether they appear accurate/recent) - URL count (note if very large or very small relative to likely site size)
- Does the target URL appear in the sitemap?
Step 3: Meta Tags Analysis
Extract and evaluate all SEO-relevant meta tags from the page HTML:
| Meta Tag | Check | Issue if Missing/Wrong |
|---|---|---|
<title> |
Present, 50-60 characters, includes primary keyword | Missing title = no search snippet control |
<meta name="description"> |
Present, 150-160 characters, compelling, includes keyword | Missing = Google generates its own |
<link rel="canonical"> |
Present, self-referencing or pointing to preferred version | Missing = potential duplicate content |
<meta name="robots"> |
Check for noindex, nofollow, noarchive, nosnippet, max-snippet | noindex = page excluded from search |
<meta name="viewport"> |
Present with width=device-width, initial-scale=1 |
Missing = mobile usability failure |
<html lang="..."> |
Present with correct language code | Missing = language detection issues |
| Open Graph tags | og:title, og:description, og:image, og:url, og:type | Missing = poor social/AI preview |
| Twitter Card tags | twitter:card, twitter:title, twitter:description, twitter:image | Missing = poor X/Twitter preview |
<link rel="alternate" hreflang="..."> |
Present if multilingual site | Missing on multilingual = wrong language served |
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.
- 11d ago First seen · 304 lines · 42 tokens per session scan A f80ea4765ca3
geo-technical is an agent published in the GitHub repository TheSmokeDev/geo-skills (22 stars, last pushed 7d ago), licensed MIT. It adds 42 tokens to every session and 3,487 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to geo-technical, differing in 42 lines, and is treated as a copy.
Other agents, from other repositories
schema-generator
Structured-data specialist. Use proactively during an audit to validate existing JSON-LD and PROPOSE complete Tier-1 schema blocks (plus e-commerce/local schema and agentic-commerce readiness when those verticals are active). It proposes diffs only and does NOT write files.
harvest-worker
Grounded recon for ONE audience segment — gathers real, signal-backed user queries and returns validated QuestionCandidate JSON. Never writes questions.csv, never touches the DB. Spawned by the open-geo orchestrator (STEP A.5, Phase A).
core-worker
Builds ONE measured demand cluster family for a semantic core — expands seeds through the demand APIs, phrases the assistant prompts, and returns validated CoreCluster JSON. No browser, never writes the core or the CSV. Spawned by the semantic-core orchestrator (STEP 4).
seo-fixer-writer
The ONLY agent allowed to write files. Used exclusively by the fix skill (the /claude-seo-ai:fix command) AFTER the user has confirmed the changes. Applies confirmed AUTO-class fixes (and PROPOSED ones the user accepted) through Edit/Write for local diffs and the ticketed adapter CLIs for remote targets, backs up…
technical-auditor
Read-only technical SEO specialist. Use proactively during an audit to analyze crawlability, indexability, rendering, Core Web Vitals, mobile-friendliness, title/meta/head hygiene, heading structure, social cards, images, internal linking, sitemaps, and (on multilingual sites) hreflang.
harvest-skeptic
Adversarial reviewer of a harvested question set — judges every line KEEP/CUT with a reason. Spawned by the open-geo orchestrator (STEP A.5, Phase C). Never edits files, never runs the capture.