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 olelehmann1337/workshop-plugin --skill seo-audit-v2git clone --depth 1 https://github.com/olelehmann1337/workshop-pluginWrote 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/olelehmann1337/workshop-plugin/seo-audit-v2)<a href="https://agentmods.dev/skills/olelehmann1337/workshop-plugin/seo-audit-v2"><img src="https://agentmods.dev/badge/skills/olelehmann1337/workshop-plugin/seo-audit-v2.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.00148 | $0.01926 |
| Opus 5 | $0.00074 | $0.00963 |
| Sonnet 5 | $0.00030 | $0.00385 |
| Haiku 4.5 | $0.00015 | $0.00193 |
Grade A, and why
seo-audit-v2 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 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.
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Audit
Most SEO tools promise 148 rules and deliver a PDF nobody reads. For a non-technical marketer, the ranking wins live in about 20 of those rules: title, meta, H1, canonical, social cards, schema, alt text, internal links. This skill checks exactly those, on any URL, with nothing to install.
the core job
Pull a public webpage's HTML, parse the on-page SEO signals, grade the result A-F, and hand back a priority-ordered fix list with exact code snippets. Every audit ends with a clear "what I did NOT check" disclosure so the user knows where the audit's edges are.
Output format: A single markdown report per URL (or one summary + per-URL reports for multi-page runs). Graded, prioritized P0-P3, with copy-paste fixes.
before starting: gather context
STOP. Do not start fetching or parsing until every field below is confirmed with the user. Ask for any missing field first. Do not guess the URL, do not assume single vs multi-page.
- Target URL(s) — Which URL? Up to 10 for a batch. (Required — without this there's nothing to audit.)
- Specific concern — Anything they're worried about? Like "we dropped in Google rankings last week" or "I just redesigned this page." (Optional, but changes which findings get lead-billing in the report.)
- Target keyword — Is there a specific keyword they're trying to rank for on this page? (Optional, but unlocks title/H1/meta keyword checks.)
Once confirmed, before running WebFetch, state the audit's scope caveat in one line so they don't walk away with wrong expectations:
"This covers on-page SEO only — no Core Web Vitals, page speed, or security headers. If you need those, run Google PageSpeed Insights on the same URL."
fetch: pull the page and its robots/sitemap
For each URL:
WebFetchthe page itself.WebFetchhttps://{domain}/robots.txtWebFetchhttps://{domain}/sitemap.xml(or whatever the robots.txtSitemap:directive points to)
Sanity check before parsing: Confirm the HTML contains real content. If the <body> is empty or contains only <script> tags (common on React/Vue SPAs without SSR), stop and tell the user:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 168 lines · 148 tokens per session scan A d08127d361aa
seo-audit-v2 is a skill published in the GitHub repository olelehmann1337/workshop-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 148 tokens to every session and 1,926 once invoked, about $0.0007 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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…