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 arozumenko/sdlc-skills --skill content-seo-auditgit clone --depth 1 https://github.com/arozumenko/sdlc-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/arozumenko/sdlc-skills/content-seo-audit)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/content-seo-audit"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/content-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/arozumenko/sdlc-skills/content-seo-audit"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/content-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.00035 | $0.00522 |
| Opus 5 | $0.00017 | $0.00261 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
content-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.
What it actually says
Content & SEO Analysis
Content ✍️ specialist pass.
Data Sources
browser_snapshot() — the page title is typically visible in the
snapshot/document root; use it for the <title> check.
browser_take_screenshot() — visual review for copy quality, typos,
CTA wording, and headings.
Limitation: the factory's Playwright MCP toolset has no browser_evaluate,
so <meta> tags (description, robots, canonical, viewport), Open
Graph/Twitter Card tags, and structured data (JSON-LD) cannot be read
directly — they aren't exposed by browser_snapshot. Report meta-tag
findings only when they can be corroborated some other way (e.g. a visibly
broken/missing OG image on a shared-link preview, or a noindex banner shown
by an SEO extension in the screenshot); otherwise state that the specific meta
tag could not be verified in this environment and skip it rather than guessing.
Never claim to have read a meta tag's content without evidence.
Focus Areas
- Typos and grammatical errors
- Inconsistent tone/voice
- Vague CTAs ("Click here", "Submit")
- Missing/misleading headings
- Placeholder text left in ("Lorem ipsum", "TODO")
- Unclear value proposition
- Broken links in body text
SEO Meta Checks
Verify only what's directly observable per the Limitation above (primarily the
<title>); flag the rest as unverifiable rather than reporting a finding.
| Element | Priority |
|---|---|
<title> |
p1 |
meta description |
p1 |
og:title + og:image |
p2 |
canonical URL |
p2 |
robots = noindex on live page |
p0 |
| Structured data (JSON-LD) | p2 |
twitter:card |
p3 |
Output
SEO issues = p0-p1. Content quality issues = p2-p3 unless in critical CTAs.
Produce findings in the shared schema — see the qa-auditor audit-methodology.md.
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 · 61 lines · 35 tokens per session scan A 53a0ea91cd3b
content-seo-audit is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 522 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…