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 lisbeth718/pseo-skills --skill seo-regression-guardgit clone --depth 1 https://github.com/lisbeth718/pseo-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/lisbeth718/pseo-skills/seo-regression-guard)<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/seo-regression-guard"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/seo-regression-guard/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/lisbeth718/pseo-skills/seo-regression-guard"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/seo-regression-guard.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.00075 | $0.02489 |
| Opus 5.5 | $0.00030 | $0.00996 |
| Sonnet 5.5 | $0.00015 | $0.00498 |
| Haiku 4.5 | $0.00007 | $0.00249 |
Grade A, and why
seo-regression-guard 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 6d 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.
until curl -sf localhost:3000 >/dev/null; do sleep 1; done How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Regression Guard
Catches the silent breakages that kill indexing: a template starts returning 200 for missing data, canonical moves out of <head>, a noindex leaks to production, robots.txt blocks the sitemap, titles collapse to one string. Samples URLs per template from the sitemap, checks them, and diffs against a saved baseline. Fails with exit code 1 on errors or regressions.
No GitHub Actions needed. Run it by hand, from a git hook, or as the last step of the deploy script. The bundled script is scripts/seo-check.ts (Node 20+, no dependencies, run with npx tsx).
Quick start
Script location depends on how the skill is installed. Either use the installed path (.claude/skills/seo-regression-guard/scripts/seo-check.ts, below as $SEO_CHECK), or copy it to your project's scripts/ and add tsx as a devDependency (npm i -D tsx), then run npx tsx scripts/seo-check.ts.
SEO_CHECK=.claude/skills/seo-regression-guard/scripts/seo-check.ts
# 1. Against a local production build (pre-deploy)
npm run build && (npm start & echo $! > .seo-server.pid)
until curl -sf localhost:3000 >/dev/null; do sleep 1; done
npx tsx $SEO_CHECK --site http://localhost:3000 --baseline .seo-baseline.json; code=$?
kill "$(cat .seo-server.pid)"; rm .seo-server.pid; exit $code
# 2. Against the live site after deploy
npx tsx $SEO_CHECK --site https://example.com --baseline .seo-baseline.json
# 3. Accept the current state as the new baseline (after an intended change)
npx tsx $SEO_CHECK --site https://example.com --update-baseline
(npm start may leave child processes; if the port stays busy, also run pkill -f "next start".)
Flags: --per-template 5 (URLs sampled per template), --templates templates.json (path regex per template name; default groups by first segment and depth with placeholders, e.g. /jobs/*/*, and single root-level slugs as /*), --max-html-bytes 2000000, --json.
Local builds: the sitemap lists production URLs. Generate it from NEXT_PUBLIC_SITE_URL=http://localhost:3000 for the run, or the check will report sitemap-host.
What ships with it
1 file 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.
- 6d ago First seen · 117 lines · 75 tokens per session scan A 7ec60c61ef41
seo-regression-guard is a skill published in the GitHub repository lisbeth718/pseo-skills (54 stars, last pushed 6d ago), licensed MIT. It adds 75 tokens to every session and 2,489 once invoked, about $0.0003 per session on Opus 5.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-10-12.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.