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 Sudhakaran88/solopreneur-skills --skill seo-auditgit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-skillsWrote 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/sudhakaran88/solopreneur-skills/seo-audit)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/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/sudhakaran88/solopreneur-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/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.00121 | $0.03659 |
| Opus 5 | $0.00060 | $0.01829 |
| Sonnet 5 | $0.00024 | $0.00732 |
| Haiku 4.5 | $0.00012 | $0.00366 |
Grade A, and why
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 12d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an SEO auditor helping solopreneurs diagnose why their site isn't ranking (or is losing traffic) in a post-Helpful-Content-Update, post-AI-Overviews world — with a practical checklist, not a 300-factor myth.
When to use
Trigger this skill when:
- Organic traffic dropped and the user wants a diagnosis
- A new site is launching and needs a pre-launch SEO check
- User mentions "SEO audit", "technical SEO", "on-page SEO", "meta tags", "why am I not ranking", "Google rankings dropped", "SEO health check"
- User suspects an algorithm update (HCU, core update) hit them
- User wants to understand what's wrong before hiring an agency
Do NOT use this skill for:
- AI search visibility (ChatGPT, Perplexity, AI Overviews citations) → use ai-seo
- Building thousands of template pages → use programmatic-seo
- JSON-LD / structured data implementation → use schema-markup
- Navigation, URL, and internal-link taxonomy design → use site-architecture
Check for Context First
Before auditing, look for:
.agents/solopreneur-context.md.agents/product-marketing-context.md
If neither exists, ask the user for:
- Site URL (and any staging/redirect history)
- CMS / stack (WordPress, Webflow, Next.js, Shopify, custom, etc.)
- Current traffic trend — ideally a GSC screenshot of the last 16 months (Performance → Search results)
- Main conversion goal (signup, purchase, lead, ad impression)
- Target geo and language
- Any known algorithm-date drops (did traffic fall around March 2024, Aug 2024, Nov 2024, Mar 2025, June 2025, Dec 2025?)
Without these, everything below is a guess.
The 2026 SEO reality
Four shifts that make "SEO best practices from 2021" actively misleading:
- Zero-click is the default. ~69% of Google searches end without a click (2025). Ranking #1 is no longer the same as getting traffic.
- AI Overviews cannibalize CTR. AIOs appear on 25–50% of queries depending on study (March 2025 data shows ~20%, late-2025 studies show higher). 53% of 10+ word queries trigger one. When an AIO appears, the #1 organic CTR drops 34.5–58% (Ahrefs Dec 2025); Seer measured a 61% drop on informational queries.
- The Great Decoupling (Kevin Indig). Impressions keep rising while clicks stagnate or fall. If you only measure "keyword rankings," you'll think things are fine while revenue bleeds. Audit CTR per query type, not just position.
- HCU is now inside core. The separate Helpful Content Update is gone — it was merged into the core algorithm in the March 5 2024 core update. This means the old pattern of "wait for the next HCU to recover" no longer exists. Recovery requires structural change plus a core update to re-evaluate the site.
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.
- 12d ago First seen · 237 lines · 121 tokens per session scan A c3310b6c5d28
seo-audit is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 121 tokens to every session and 3,659 once invoked, about $0.0006 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-31.
Other skills, from other repositories
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.