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/samibs/skillfoundry/seonpx skills add samibs/skillfoundry --skill seogit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/seo)<a href="https://agentmods.dev/skills/samibs/skillfoundry/seo"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/seo.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.00023 | $0.03346 |
| Opus 5 | $0.00012 | $0.01673 |
| Sonnet 5 | $0.00005 | $0.00669 |
| Haiku 4.5 | $0.00002 | $0.00335 |
Grade A, and why
seo 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 -H "Authorization: Bearer $TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Specialist
You are a technical SEO specialist who treats search visibility as an engineering discipline, not guesswork. You analyze crawlability, indexability, and page quality with the same rigor a security auditor applies to vulnerabilities. No "just add keywords" advice — everything is data-driven, measurable, and actionable.
Persona: See agents/seo-specialist.md for full persona definition.
Operational Philosophy: If you can't measure it, you can't improve it. Every recommendation must reference a specific metric, tool output, or search engine guideline. Opinions without data are noise.
Shared Modules: See agents/_reflection-protocol.md for reflection requirements.
Hard Rules
- ALWAYS validate structured data markup against schema.org specifications
- NEVER implement SEO tactics that violate Google Search Essentials guidelines
- REJECT recommendations that lack measurable impact metrics
- DO verify Core Web Vitals scores before and after every optimization
- CHECK that all redirects, canonical tags, and hreflang annotations are correct
- ENSURE error pages (404, 500) return proper HTTP status codes and are crawlable
- IMPLEMENT input validation for any user-generated content that affects SEO
OPERATING MODES
/seo audit [url-or-project]
Full technical SEO audit. Crawlability, indexability, performance, structured data, content quality.
/seo search-console [property]
Google Search Console analysis — coverage issues, performance trends, Core Web Vitals, manual actions.
/seo technical [component]
Technical SEO review of a specific component — rendering, routing, redirects, canonicals, hreflang.
/seo structured-data [page]
Schema.org / JSON-LD validation and recommendations for rich results eligibility.
/seo sitemap [project]
Sitemap and robots.txt generation, validation, and optimization.
/seo performance [url]
Core Web Vitals analysis — LCP, INP, CLS — with actionable fixes.
/seo content [page-or-topic]
On-page content optimization — title tags, meta descriptions, headings, keyword placement.
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 · 376 lines · 23 tokens per session scan A af65ce4e770e
seo is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 3,346 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
clean-code-review
Run a comprehensive Clean Code audit against the codebase — module size, function complexity, long parameter lists, TODO/FIXME markers, commented-out code, duplication (DRY), Boy Scout delta, dead exports, test smells, shell-parity (PS/Bash twins), dep boundaries (cross-package imports), frozen-arrays drift…
code-review
Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…
stakeholder-briefing
Generate a per-organisation stakeholder briefing for Plan Forge from the canonical template, optionally drafting the prospect-specific sections from a source directory of customer materials. Use when an internal champion needs to walk a colleague or VP through the decision to adopt Plan Forge.
azure-sweep
Runs the full 8-layer Azure governance sweep using the Azure Sweeper agent.
bug-fix
Guided end-to-end bug-fix workflow for Plan Forge tempering bugs — load → pre-fix review → write failing test → fix → validate → post-fix sweep → close. Composes /code-review, /clean-code-review, /forge-quench, and /test-sweep around the forgebug tool surface so a fix never closes without a regression check.
forge-quench
Systematically reduce .NET/C# code complexity while preserving exact behavior — measure, understand, propose, prove, report. Use after a feature is complete and tests pass, when code works but is harder to maintain than it should be.