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/resciencelab/opc-skills/seo-geonpx skills add ReScienceLab/opc-skills --skill seo-geogit clone --depth 1 https://github.com/ReScienceLab/opc-skillsWhat 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.00060 | $0.02116 |
| Opus 5 | $0.00030 | $0.01058 |
| Sonnet 5 | $0.00012 | $0.00423 |
| Haiku 4.5 | $0.00006 | $0.00212 |
Grade A, and why
seo-geo 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 yesterday.
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.
curl -sL "https://example.com" | grep -E "<title>|<meta name=\"description\"|<meta property=\"og:|application/ld\+json" | head -20 Copies of this mod
1 near-identical copy found in the catalogue:
- seo-geo — 91% identical, 104 lines differ
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO/GEO Optimization Skill
Comprehensive SEO and GEO (Generative Engine Optimization) for websites. Optimize for both traditional search engines (Google, Bing) and AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude).
Quick Reference
GEO = Generative Engine Optimization - Optimizing content to be cited by AI search engines.
Key Insight: AI search engines don't rank pages - they cite sources. Being cited is the new "ranking #1".
Workflow
Step 1: Website Audit
Get the target URL and analyze current SEO/GEO status.
Basic SEO Audit (Free):
python3 scripts/seo_audit.py "https://example.com"
Use this for: Quick technical SEO check (title, meta, H1, robots, sitemap, load time). No API needed.
Check Meta Tags:
curl -sL "https://example.com" | grep -E "<title>|<meta name=\"description\"|<meta property=\"og:|application/ld\+json" | head -20
Use this for: Quick check of essential meta tags and schema markup on any webpage.
Check robots.txt:
curl -s "https://example.com/robots.txt"
Use this for: Verify which bots are allowed/blocked. Critical for ensuring AI search engines can crawl your site.
Check sitemap:
curl -s "https://example.com/sitemap.xml" | head -50
Use this for: Verify sitemap structure and ensure all important pages are included for search engine discovery.
Verify AI Bot Access:
# These bots should be allowed in robots.txt:
- Googlebot (Google)
- Bingbot (Bing/Copilot)
- PerplexityBot (Perplexity)
- ChatGPT-User (ChatGPT with browsing)
- ClaudeBot / anthropic-ai (Claude)
- GPTBot (OpenAI)
Step 2: Keyword Research
Use WebSearch to research target keywords:
WebSearch: "{keyword} keyword difficulty site:ahrefs.com OR site:semrush.com"
WebSearch: "{keyword} search volume 2026"
WebSearch: "site:{competitor.com} {keyword}"
Analyze:
- Search volume and difficulty
- Competitor keyword strategies
- Long-tail keyword opportunities
- International keyword conflicts (e.g., "OPC" = industrial automation in English markets)
What ships with it
17 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.
- examples/opc-skills-case-study.md 7.7 KB
- references/geo-research.md 9.1 KB
- references/google-docs-summary.md 1.5 KB
- references/platform-algorithms.md 11 KB
- references/schema-templates.md 11 KB
- references/seo-checklist.md 7.1 KB
- references/tools-and-apis.md 8.0 KB
- scripts/autocomplete_ideas.py 2.5 KB runs code
- scripts/backlinks.py 1.0 KB runs code
- scripts/competitor_gap.py 3.0 KB runs code
- scripts/credential.py 311 B runs code
- scripts/dataforseo_api.py 3.2 KB runs code
- scripts/domain_overview.py 1.4 KB runs code
- scripts/keyword_research.py 1.1 KB runs code
- scripts/related_keywords.py 3.1 KB runs code
- scripts/seo_audit.py 4.8 KB runs code
- scripts/serp_analysis.py 1.2 KB runs code
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.
- yesterday First seen · 269 lines · 60 tokens per session scan A 1bcce31ac3d4
seo-geo is a skill published in the GitHub repository ReScienceLab/opc-skills (1,710 stars, last pushed 2d ago), licensed Apache-2.0. It adds 60 tokens to every session and 2,116 once invoked, about $0.0003 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
context-okf-llm-ingest
Use when extracting a codebase's implementation decisions into Metatron with an LLM/agent instead of metatron ingest — authoring candidate decisions as Open Knowledge Format (OKF) markdown files locally for review.
context-okf-promote-candidates
Use when promoting reviewed Metatron candidate decisions to canonical in a git/CI flow — moving Open Knowledge Format (OKF) files from candidate/ to decisions/. The agent performs only human-named moves; it never decides what to promote.
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
live-audit
Repo-specific playbook, for any agent/model working on this repo (not tied to a particular harness — see AGENTS.md's own framing). Use it when asked to test/audit/smoke-test the published tmdb-mcp package, hunt for bugs or edge cases, or repeat "the same kind of testing as before.".
prompt-check
Live-test every MCP Prompt in src/tools/prompts.ts through the real MCP protocol (not a static read) across every argument combination. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.
prompt-check
Live-test every MCP Prompt in src/prompts.ts through the real MCP protocol (not a static read) across every argument combination, including every enum value. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.