Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fortunto2/solo-factory/plugin install soloWrote 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-cli)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/seo-cli"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/seo-cli.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.1 | $0.00180 | $0.06477 |
| Opus 5 | $0.00090 | $0.03238 |
| Sonnet 5 | $0.00036 | $0.01295 |
| Haiku 4.5 | $0.00018 | $0.00648 |
Grade A, and why
solo-seo-cli 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 8d 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.
curl -s "https://ssl.bing.com/webmaster/api.svc/json/GetUserSites?apikey=$KEY" | head -c 200 How it starts
The opening of the file, as written. The whole thing — 529 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO CLI Skill
Unified search engine management and SEO/GEO auditing for all configured sites.
Running it
seo is installed globally as a wrapper at ~/.local/bin/seo. Just call it:
seo audit https://example.com
If the command is missing, recreate the wrapper (the project keeps cli.py and config.yaml side
by side and is not packaged for uv tool install — a global install fails with
ModuleNotFoundError: No module named 'cli'):
cat > ~/.local/bin/seo <<'EOF'
#!/bin/sh
SEO_HOME="$HOME/startups/shared/seo-cli"
exec "$SEO_HOME/.venv/bin/python" "$SEO_HOME/cli.py" "$@"
EOF
chmod +x ~/.local/bin/seo
Source lives in ~/startups/shared/seo-cli/. Do not build a SEO=... shell variable holding
two words — in zsh it is not word-split and the call fails.
Commands
Audit — SEO+GEO health check
# Summary table across ALL sites (fast, no PageSpeed)
seo audit
# Detailed single-site audit with PageSpeed + keywords
seo audit https://superduperai.co
Agent audit — what an AI agent can discover, read and act on
seo agent-audit # every configured site
seo agent-audit https://example.com # one site, full detail
A site now has two audiences, and this checks the second: robots rules naming GPTBot and friends, Content-Signals, llms.txt, markdown negotiation, MCP and A2A cards.
It probes a path that cannot exist before anything else. A great many sites answer 200 with their home page for every URL, and a checker that trusts status codes then reports a perfect score for a site that has none of it — life2film.com scored 12/12 that way while every response was the same HTML page. Its real score was 5. When that probe returns 200 the report says so at the top and verifies content instead: JSON must parse, text must not be HTML.
Markdown negotiation is tested on the home page and on a real page from the sitemap. Sites
whose root is an index have no markdown twin for it while every article does, and probing only
/ calls that "no negotiation" — the same false negative pointing the other way.
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.
- 8d ago First seen · 529 lines · 180 tokens per session scan A d0769cc643e5
solo-seo-cli is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 180 tokens to every session and 6,477 once invoked, about $0.0009 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
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.
review
L1 internal review with auto-detection, design comparison, and Gate escalation path.
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-refresh
Review stale, duplicated, obsolete, or unused target harness guidance. Use when the user asks for /harness refresh or wants harness maintenance recommendations without default edits.