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-llmstxtgit 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-llmstxt)<a href="https://agentmods.dev/skills/thesmokedev/geo-skills/geo-llmstxt"><img src="https://agentmods.dev/badge/skills/thesmokedev/geo-skills/geo-llmstxt/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-llmstxt"><img src="https://agentmods.dev/badge/skills/thesmokedev/geo-skills/geo-llmstxt.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.00076 | $0.03947 |
| Opus 5 | $0.00038 | $0.01973 |
| Sonnet 5 | $0.00015 | $0.00789 |
| Haiku 4.5 | $0.00008 | $0.00395 |
Grade A, and why
geo-llmstxt 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 13d 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
86% identical to geo-llmstxt — 28 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
llms.txt Standard Analysis and Generation Skill
Purpose
This skill handles everything related to the llms.txt convention (proposed by Jeremy Howard in September 2024) -- a single Markdown file at the domain root that states your canonical business facts and points at your most important pages.
Positioning as of August 2026: llms.txt is a 30-minute anti-hallucination facts hedge, NOT an AI-visibility lever. Do not sell it to clients as a ranking or citation play -- the evidence says it does not move citations:
- Google Search Central, 2026 (official): "You don't need to create new machine readable files... to appear in generative AI search." Google has stated plainly that no AI-specific file is required or rewarded.
- Zyppy meta-analysis of 54 studies (via digitalapplied.com, Jun 2026): llms.txt scores 2.0 out of 10 -- the lowest of all 23 measured GEO factors.
- SE Ranking (seranking.com/blog/llms-txt, Nov 2025): found zero correlation between having an llms.txt file and AI citation/visibility.
What llms.txt Is Actually For
What remains is real but modest. A well-crafted llms.txt is worth roughly 30 minutes of effort because it:
- Reduces misrepresentation: Key facts (pricing, features, locations, founding date) are stated explicitly in one place, reducing AI hallucination about your business when a system does consult the file.
- Controls the narrative: You choose which pages and facts are presented as canonical, rather than leaving inference to a crawler.
- Costs almost nothing: It is a single static Markdown file. There is no maintenance burden beyond updating it when facts change.
What it does not do: improve rankings, increase citation rates, or substitute for indexation, crawlability, or content quality. Treat it as hygiene -- like a favicon or a humans.txt with a purpose -- and never present it in an audit as a visibility win.
The llms.txt Specification
File Location
The file MUST be located at the root of the domain:
https://example.com/llms.txt
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.
- 13d ago First seen · 439 lines · 76 tokens per session scan A 5cbc83068480
geo-llmstxt is a skill published in the GitHub repository TheSmokeDev/geo-skills (22 stars, last pushed 9d ago), licensed MIT. It adds 76 tokens to every session and 3,947 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to geo-llmstxt, differing in 28 lines, and is treated as a copy.
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…