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 agentmods add skills/felipeslo/opencode-kit/geo-fundamentalsnpx skills add felipeslo/opencode-kit --skill geo-fundamentalsgit clone --depth 1 https://github.com/felipeslo/opencode-kitWrote 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/felipeslo/opencode-kit/geo-fundamentals)<a href="https://agentmods.dev/skills/felipeslo/opencode-kit/geo-fundamentals"><img src="https://agentmods.dev/badge/skills/felipeslo/opencode-kit/geo-fundamentals.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00847 |
| Opus 5 | $0.00012 | $0.00424 |
| Sonnet 5 | $0.00005 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
geo-fundamentals 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 4d 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
97% identical to geo-fundamentals — 1 line 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEO Fundamentals
Optimization for AI-powered search engines.
1. What is GEO?
GEO = Generative Engine Optimization
| Goal | Platform |
|---|---|
| Be cited in AI responses | ChatGPT, Claude, Perplexity, Gemini |
SEO vs GEO
| Aspect | SEO | GEO |
|---|---|---|
| Goal | #1 ranking | AI citations |
| Platform | AI engines | |
| Metrics | Rankings, CTR | Citation rate |
| Focus | Keywords | Entities, data |
2. AI Engine Landscape
| Engine | Citation Style | Opportunity |
|---|---|---|
| Perplexity | Numbered [1][2] | Highest citation rate |
| ChatGPT | Inline/footnotes | Custom GPTs |
| Claude | Contextual | Long-form content |
| Gemini | Sources section | SEO crossover |
3. RAG Retrieval Factors
How AI engines select content to cite:
| Factor | Weight |
|---|---|
| Semantic relevance | ~40% |
| Keyword match | ~20% |
| Authority signals | ~15% |
| Freshness | ~10% |
| Source diversity | ~15% |
4. Content That Gets Cited
| Element | Why It Works |
|---|---|
| Original statistics | Unique, citable data |
| Expert quotes | Authority transfer |
| Clear definitions | Easy to extract |
| Step-by-step guides | Actionable value |
| Comparison tables | Structured info |
| FAQ sections | Direct answers |
5. GEO Content Checklist
Content Elements
- Question-based titles
- Summary/TL;DR at top
- Original data with sources
- Expert quotes (name, title)
- FAQ section (3-5 Q&A)
- Clear definitions
- "Last updated" timestamp
- Author with credentials
Technical Elements
- Article schema with dates
- Person schema for author
- FAQPage schema
- Fast loading (< 2.5s)
- Clean HTML structure
6. Entity Building
| Action | Purpose |
|---|---|
| Google Knowledge Panel | Entity recognition |
| Wikipedia (if notable) | Authority source |
| Consistent info across web | Entity consolidation |
| Industry mentions | Authority signals |
What ships with it
1 file 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.
- 4d ago First seen · 156 lines · 24 tokens per session scan A cd8cf065f2a0
geo-fundamentals is a skill published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 847 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to geo-fundamentals, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…