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 fortunto2/solo-factory --skill seo-auditgit clone --depth 1 https://github.com/fortunto2/solo-factoryWrote 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/fortunto2/solo-factory/seo-audit)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/seo-audit"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/seo-audit/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/fortunto2/solo-factory/seo-audit"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/seo-audit.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.00056 | $0.01974 |
| Opus 5 | $0.00028 | $0.00987 |
| Sonnet 5 | $0.00011 | $0.00395 |
| Haiku 4.5 | $0.00006 | $0.00197 |
Grade A, and why
solo-seo-audit 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/seo-audit
SEO health check for any URL or project landing page. Fetches the page, analyzes meta tags, OG, JSON-LD, sitemap, robots.txt, checks SERP positions for target keywords, and outputs a scored report.
seo-cli (use if available)
Dedicated SEO CLI — repo: https://github.com/fortunto2/seo-cli
# Install (one-time)
git clone https://github.com/fortunto2/seo-cli.git ~/startups/shared/seo-cli
cd ~/startups/shared/seo-cli && uv venv && uv pip install -e .
cp config.example.yaml config.yaml # add credentials (GSC, Bing, Yandex, IndexNow)
# Detect seo-cli
python ~/startups/shared/seo-cli/cli.py --help 2>/dev/null
If available, prefer seo-cli commands over manual WebFetch:
python ~/startups/shared/seo-cli/cli.py audit <url>— deep page audit (meta, OG, JSON-LD, keywords, readability)python ~/startups/shared/seo-cli/cli.py status— dashboard for all registered sitespython ~/startups/shared/seo-cli/cli.py analytics <site>— GSC data (queries, impressions, CTR)python ~/startups/shared/seo-cli/cli.py monitor <site>— position tracking with snapshotspython ~/startups/shared/seo-cli/cli.py reindex <url>— instant reindex via Google Indexing API + IndexNowpython ~/startups/shared/seo-cli/cli.py competitors <keyword>— SERP + competitor analysispython ~/startups/shared/seo-cli/cli.py launch <site>— full new site promotion workflow
If seo-cli is not available, fall back to WebFetch-based audit below.
MCP Tools (use if available)
web_search(query, engines, include_raw_content)— SERP position check, competitor analysisproject_info(name)— get project URL if auditing by project name
If MCP tools are not available, use Claude WebSearch/WebFetch as fallback.
Steps
- Parse target from
$ARGUMENTS.- If URL (starts with
http): use directly. - If project name: look up URL from project README, CLAUDE.md, or
docs/prd.md. - If empty: ask via AskUserQuestion — "Which URL or project to audit?"
- If URL (starts with
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.
- 11d ago First seen · 167 lines · 56 tokens per session scan A 531619b825a1
solo-seo-audit is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,974 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
review
L1 internal review with auto-detection, design comparison, and Gate escalation path.
harness
Route Harness Starter Kit workflows. Use when the user invokes /harness with adopt, doctor, update, refresh, review, or review sub-agent, or asks to apply, diagnose, maintain, or review repository harness guidance.
dev-plan
Generate a development plan with task breakdown and section 10 tracking tables.
product-diagnosis
Six-question diagnostic framework for G0 pre-check — validate product direction before development starts.
harness-adopt
Apply Harness Starter Kit prompt-first adoption to a target repository. Use when the user asks to apply, install, adopt, or bootstrap repository harness guidance, checks, memory, and adoption reporting.
harness-update
Refresh an adopted target repository from the latest Harness Starter Kit reference. Use when the user asks for /harness update or wants source tracking and selective harness updates.