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 joaoguirunas/team-os --skill seo-sxogit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/seo-sxo)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/seo-sxo"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/seo-sxo/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/joaoguirunas/team-os/seo-sxo"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/seo-sxo.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.00089 | $0.02493 |
| Opus 5.5 | $0.00036 | $0.00997 |
| Sonnet 5.5 | $0.00018 | $0.00499 |
| Haiku 4.5 | $0.00009 | $0.00249 |
Grade A, and why
seo-sxo 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 20d 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.
- [ ] Target URL was fetched via `"${CLAUDE_PROJECT_DIR}/.claude/skills/seo/scripts/claude-seo" run render_page.py <URL> --mode auto` (not raw curl/fetch) This is a copy
89% identical to seo-sxo — 15 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Experience Optimization (SXO)
SXO bridges the gap between SEO (what Google rewards) and UX (what users need). Traditional SEO audits check technical health. SXO asks: "Does this page deserve to rank for this keyword based on what Google is actually rewarding in the SERP?"
Core Insight
A page can score 95/100 on technical SEO and still fail to rank because it is the wrong page type for the keyword. If Google shows 8 product pages and 2 comparison pages for your keyword, your blog post will never break through -- no matter how well-optimized it is.
Commands
| Command | Purpose |
|---|---|
/seo sxo <url> |
Full SXO analysis (auto-detect keyword from page) |
/seo sxo <url> <keyword> |
Full SXO analysis for a specific keyword |
/seo sxo wireframe <url> |
Generate IST/SOLL wireframe with concrete placeholders |
/seo sxo personas <url> |
Persona-only scoring (skip SERP analysis) |
Execution Pipeline
Step 1: Target Acquisition
- Fetch the target URL via
"${CLAUDE_PROJECT_DIR}/.claude/skills/seo/scripts/claude-seo" run render_page.py <URL> --mode auto(SPA-aware and SSRF-safe) - Parse with
"${CLAUDE_PROJECT_DIR}/.claude/skills/seo/scripts/claude-seo" run parse_html.py <URL>to extract: title, H1, meta description, headings hierarchy, word count, schema markup, CTAs, media elements - If no keyword provided, extract primary keyword from title tag + H1 overlap
- Validate keyword is non-empty before proceeding
Step 2: SERP Backwards Analysis
Read references/page-type-taxonomy.md for classification rules.
- Search Google for the target keyword (WebSearch)
- For each of the top 10 organic results, record:
- URL and domain authority tier (brand / niche authority / unknown)
- Page type (classify using taxonomy)
- Content format (long-form, listicle, how-to, comparison, tool, video)
- Word count estimate (from snippet length and page structure)
- Schema types present (from currently supported SERP features; exclude FAQ/HowTo)
- Media signals (video carousel, image pack, thumbnail presence)
- Record SERP features present:
- Featured snippet (paragraph / list / table / video)
- People Also Ask (extract all visible questions)
- Ads (top and bottom -- count and analyze ad copy themes)
- Related searches (extract all)
- Knowledge panel / local pack / shopping results
- AI Overview presence and source types
- Calculate SERP consensus:
- Dominant page type (>60% = strong consensus, 40-60% = mixed, <40% = fragmented)
- Content depth expectations (average word count tier)
- Schema expectation (most common structured data types)
- Media expectations (video required? images critical?)
What ships with it
4 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.
- 20d ago Changed · -4 lines · -12 tokens per session 6dbecc973897
- 25d ago First seen · 255 lines · 101 tokens per session scan A c99685827c90
seo-sxo is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 89 tokens to every session and 2,493 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 89% identical to seo-sxo, differing in 15 lines, and is treated as a copy.
Other skills, from other repositories
jsonl-log-analyzer
Analyze large JSONL log files using schema-aware partitioned analysis. Discovers field schema, generates tailored jq extraction recipes, and orchestrates parallel chunk analysts with synthesis. Use when processing JSONL logs exceeding context limits, performing log analytics, or investigating incident logs.
orchestration-patterns
Apply proven orchestration patterns for agent teams including parallel specialists, pipelines, swarms, research+implementation, plan approval, and multi-file refactoring. Use when choosing a team structure, designing workflows, or implementing specific coordination patterns.
task-system
Manage shared task lists for agent teams including creating tasks, setting dependencies, claiming work, and tracking progress. Use when creating work items, building task pipelines, coordinating task ownership, or managing task dependencies.
spawn-backends
Configure how teammate agents run including in-process, tmux, and iTerm2 backends. Use when choosing a display mode, setting up split panes, troubleshooting backend issues, or configuring teammateMode.
error-handling
Debug and recover from agent team errors including common errors, hooks for quality gates, known limitations, and recovery strategies. Use when encountering team errors, enforcing quality gates with hooks, understanding limitations, or debugging agent issues.
messaging
Send messages between agents using SendMessage including direct messages, broadcasts, shutdown requests/responses, and plan approvals. Use when communicating between agents, understanding message formats, or handling structured protocol messages.