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 skills add TheSmokeDev/geo-skills --skill geo-ai-index-accessgit 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/skills/thesmokedev/geo-skills/geo-ai-index-access)<a href="https://agentmods.dev/skills/thesmokedev/geo-skills/geo-ai-index-access"><img src="https://agentmods.dev/badge/skills/thesmokedev/geo-skills/geo-ai-index-access/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/thesmokedev/geo-skills/geo-ai-index-access"><img src="https://agentmods.dev/badge/skills/thesmokedev/geo-skills/geo-ai-index-access.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 40 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00082 | $0.02180 |
| Opus 5 | $0.00041 | $0.01090 |
| Sonnet 5 | $0.00016 | $0.00436 |
| Haiku 4.5 | $0.00008 | $0.00218 |
Grade A, and why
geo-ai-index-access 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 12d 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.
1. Fetch a key page with a plain HTTP client (curl/Bash) -- no JavaScript execution. How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Index + Access Layer Skill
Purpose
This skill audits the hard technical prerequisites for AI citation: being in the right index, being crawlable by AI agents, allowing content previews, and serving content in raw HTML. None of the content-level GEO work in this pack matters if these gates are closed. Run this audit FIRST, before skills/geo-citability/, skills/geo-fanout/, or any content strategy work.
Core Insight
ChatGPT's retrieval pipeline runs on the Bing index, not Google's: 87% of ChatGPT citations match Bing top results, and Google appears nowhere in the pipeline (SubscribePR analysis, Jul 2026). A site can rank #1 on Google and be completely invisible to ChatGPT if Bing has not indexed it. Bing Webmaster Tools verification + sitemap submission + IndexNow is therefore the ChatGPT entry ticket -- and it also unlocks Bing WMT's AI Performance / Copilot citation data, one of the few first-party AI-visibility datasets available.
Beyond indexation, three access gates silently kill AI visibility:
- Crawler blocks -- robots.txt or CDN/WAF rules blocking OAI-SearchBot, GPTBot, ChatGPT-User, PerplexityBot, or ClaudeBot. ~27% of B2B sites accidentally block AI agents at the CDN level (⚠️ industry estimate -- verify before quoting publicly).
- Preview restrictions -- legacy
nosnippetor restrictivemax-snippetdirectives suppress AI citations. Scored 9.2/10 as a citation factor (Zyppy meta-analysis of 54 studies via DigitalApplied, Jun 2026). - JavaScript-only content -- ChatGPT-User reportedly performs no JavaScript rendering (⚠️ single source, SubscribePR Jul 2026). Content that only exists after client-side rendering is invisible to it.
Audit Checklist (Execute in Order)
Gate 1: Bing Indexation (ChatGPT Entry Ticket)
- Check whether the site is verified in Bing Webmaster Tools. If not, that is the #1 finding -- verification + sitemap submission is the entry ticket.
- Run
site:example.comon Bing (WebFetchhttps://www.bing.com/search?q=site:example.com) and compare the indexed-page count against the sitemap count. A large gap = indexation problem. - Spot-check 5-10 money pages: is each one indexed on Bing?
- Check whether IndexNow is implemented:
- Look for an IndexNow key file at
[domain]/[key].txt. - Check whether the CMS/build pipeline pings
https://api.indexnow.org/indexnow(or the Bing equivalent) on publish/update. - If absent, recommend IndexNow integration -- it pushes new URLs to Bing (and other participating engines) at publish time instead of waiting for crawl.
- Look for an IndexNow key file at
- Once verified, note that Bing WMT's AI Performance (Copilot) report becomes available -- first-party data on how often the site is cited in Copilot answers. This feeds
skills/geo-measurement/.
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.
- 12d ago First seen · 133 lines · 82 tokens per session scan A 57cdbb6648e6
geo-ai-index-access is a skill published in the GitHub repository TheSmokeDev/geo-skills (22 stars, last pushed 9d ago), licensed MIT. It adds 82 tokens to every session and 2,180 once invoked, about $0.0004 per session on Opus 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
orangeo-ai-visibility-skill
Audit brand AI visibility readiness and prepare OranGEO-style GEO, AEO, LLM SEO, and AI search optimization action plans. Use when asked for a Claude Code skill, Codex skill, GEO skill, generative engine optimization skill, answer engine optimization skill, AI visibility audit, AI search visibility checker, llms.txt…
ganhuo-geo-engineer
Use this Skill when the user provides an existing article, product page, tutorial, FAQ, or knowledge note and wants to rebuild it into a GEO or AI-search-friendly content asset. Use it for old-content refresh, citation-readiness improvement, answer-first restructuring, GEO upgrades, and Ganhuo AI content workflows. Do…
ai-answer-trace
Ask Claude, ChatGPT, and Gemini a question and capture the full evidence trail behind each answer: the search queries each engine ran, the pages it retrieved, and the sources it cited. The raw material of GEO measurement. Needs AI engine API keys, not an Xpoz account.
geo-visibility-check
One-shot GEO audit: does your brand appear in Claude, ChatGPT, and Gemini answers for the buyer questions that matter? Runs a prompt panel through the engines with citation tracing and reports per-prompt verdicts, who wins instead, and which sources the answers come from.
crazyseo
Measure and fix whether AI assistants (ChatGPT, Gemini, Perplexity) recommend a website. Use when someone asks "am I visible in AI search", "does ChatGPT recommend us", "why doesn't AI mention my brand", "GEO/AEO audit", "AI SEO", "llms.txt", "is my site readable by AI crawlers", or wants to know which sources AI…
xerj-code
Reference-coding with XERJ. Clone the libraries that already solved your problem, index them locally, and retrieve the exact implementation before writing code — so the agent reads passages instead of re-deriving algorithms across retry loops. Use when starting a task in an unfamiliar API, porting an algorithm, or…