Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/techhorizonlabs/thl-opennpx agentmods add skills/techhorizonlabs/thl-open/geo-technicalWrote 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/skills/techhorizonlabs/thl-open/geo-technical)<a href="https://agentmods.dev/skills/techhorizonlabs/thl-open/geo-technical"><img src="https://agentmods.dev/badge/skills/techhorizonlabs/thl-open/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/skills/techhorizonlabs/thl-open/geo-technical"><img src="https://agentmods.dev/badge/skills/techhorizonlabs/thl-open/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.00028 | $0.00823 |
| Opus 5.5 | $0.00011 | $0.00329 |
| Sonnet 5.5 | $0.00006 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
geo-technical scanned grade A with 1 finding 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 14d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Fetch each page using curl/WebFetch to get raw HTML and HTTP headers. How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEO Technical SEO Audit
Purpose
Technical SEO is the foundation of both traditional search visibility and AI search citation. A technically broken site cannot be crawled, indexed, or cited by any platform. This skill audits eight categories of technical health with specific attention to GEO requirements, most critically server-side rendering (AI crawlers do not execute JavaScript) and AI crawler access (many sites inadvertently block AI crawlers in robots.txt).
How to Use This Skill
- Collect the target URL (homepage + 2-3 key inner pages).
- Fetch each page using curl/WebFetch to get raw HTML and HTTP headers.
- Work through each of the eight categories in
references/audit-categories.md, scoring each against its rubric there. (That file also covers the IndexNow check.) - Total the category scores into the 100-point composite below.
- Generate
GEO-TECHNICAL-AUDIT.mdusingreferences/output-template.md.
The two GEO-critical categories, AI crawler access (Category 1.2) and server-side
rendering (Category 7), are where conventional SEO audits miss the most. A site can pass a
traditional audit and still be invisible to AI crawlers because its content is client-rendered or
GPTBot is disallowed. Always confirm these two by fetching raw HTML with curl (no JS execution).
Overall Scoring
| Category | Max Points | Weight |
|---|---|---|
| Crawlability | 15 | Core foundation |
| Indexability | 12 | Core foundation |
| Security | 10 | Trust signal |
| URL Structure | 8 | Crawl efficiency |
| Mobile Optimization | 10 | Google requirement |
| Core Web Vitals | 15 | Ranking signal |
| Server-Side Rendering | 15 | GEO critical |
| Page Speed & Server | 15 | Performance |
| Total | 100 |
Per-category point breakdowns live alongside each category's checks in
references/audit-categories.md.
Score Interpretation
- 90-100: Excellent. Technically sound for both traditional SEO and GEO
- 70-89: Good. Minor issues to address but fundamentally solid
- 50-69: Needs Work. Significant technical debt impacting visibility
- 30-49: Poor. Major issues blocking crawling, indexing, or AI visibility
- 0-29: Critical. Fundamental technical failures requiring immediate attention
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed 12e0960b2e6f
- 1mo ago First seen · 72 lines · 28 tokens per session scan A a80508de5c97
geo-technical is a skill published in the GitHub repository techhorizonlabs/thl-open (17 stars, last pushed 14d ago), licensed MIT. It adds 28 tokens to every session and 823 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
geo-technical
Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access.
geo-technical
Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access.
geo-technical
Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access.
geo-technical
Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access.
seo-content-blog
Spec, audit, competitor benchmark and build for blog articles and the blog template, so a post ranks on Google and gets cited by AI engines (ChatGPT, Perplexity, AI Overviews). Input: a keyword, topic, draft or post URL. Phase 1 spec: BLOG rows on top of the common page spec, covering the 12-element answer-first…
seo-content-collection-page
Spec, audit, competitor benchmark and build for e-commerce collection, category and product listing pages (PLPs) on Shopify, WooCommerce, Magento, BigCommerce, PrestaShop or a custom store. Runs four phases: the collection spec (COL-01 to COL-24 plus the common rows), an audit of the live page with the bundled…