pseo-quality-guard

pseo-quality-guard is a skill for Claude Code from lisbeth718/pseo-skills. It costs 76 tokens per session (2,808 once invoked), scanned A, original, MIT.

A checker for programmatically generated search pages, often called pSEO pages. It looks for thin, repeated, or competing pages that may provide little distinct value to visitors.

In plain words
What is it for?
It helps audit page length, uniqueness, metadata, duplicate content, and keyword overlap across generated pages.
Why use it?
It catches quality problems before pages are published or indexed by search engines.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { getAllSlugs, getPageData } from "../lib/data";.

Good fit It helps audit page length, uniqueness, metadata, duplicate content, and keyword overlap across generated pages.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/lisbeth718/pseo-skills
agentmods
npx agentmods add skills/lisbeth718/pseo-skills/pseo-quality-guard

Made for: Claude Code.

Wrote 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.

agentmods badge for pseo-quality-guard

README.md
[![agentmods](https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-quality-guard/github.svg)](https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-quality-guard)
Your own site
<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-quality-guard"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-quality-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.

agentmods 80×15 button for pseo-quality-guard

Your own site · 80×15
<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-quality-guard"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-quality-guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,808 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.02808
Opus 5 $0.00038 $0.01404
Sonnet 5 $0.00015 $0.00562
Haiku 4.5 $0.00008 $0.00281

Measured 9d ago against content hash 1464ec8be27c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

pseo-quality-guard 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 9d 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.

skills/pseo-quality-guard/SKILL.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

pSEO Quality Guard

Validate generated pages against SEO quality standards. Detect and flag issues that would cause Google to devalue, deindex, or penalize programmatic pages.

Core Principles

  1. No thin pages: Every page must provide substantial, unique value
  2. No duplicate content: No two pages should have the same or near-identical content
  3. No cannibalization: No two pages should target the same keyword or intent
  4. Metadata uniqueness: Every page has unique title and description
  5. Fail loudly: Quality issues should block deployment, not slip through silently

Quality Checks

1. Thin Content Detection

A page is thin if it:

  • Has fewer than 300 words of unique text content (excluding navigation, footer, boilerplate)
  • Is essentially a template with only 1-2 variable substitutions
  • Contains no meaningful content beyond its metadata
  • Has the same paragraph structure as other pages with only proper nouns changed

How to check:

  • Extract text content from each rendered page (strip HTML tags, nav, footer)
  • Count unique words per page
  • Compare content across pages — compute similarity ratios
  • Flag pages with < 300 unique words or > 80% similarity to another page

2. Duplicate Content Detection

Check for:

  • Exact duplicates: Two pages with identical body content
  • Near duplicates: Pages with > 80% text similarity (use Jaccard similarity on n-grams or cosine similarity)
  • Title duplicates: Two pages with the same <title> tag
  • Description duplicates: Two pages with the same meta description
  • URL-based duplicates: Different URLs serving the same content (www vs non-www, trailing slash variants)

How to detect:

At small scale (< 200 pages), pairwise comparison is feasible:

For each pair of pages:
  similarity = intersection(ngrams(page_a), ngrams(page_b)) / union(ngrams(page_a), ngrams(page_b))
  if similarity > 0.8: FLAG as near-duplicate

At scale (200+ pages), pairwise is O(n²) and impractical. Use one of:

  • MinHash / LSH: Hash n-gram sets into fixed-size signatures, use locality-sensitive hashing to find candidate pairs. Reduces comparisons from O(n²) to near-linear.
  • SimHash: Compute a fingerprint per page, compare fingerprints (Hamming distance). Pages with similar fingerprints are candidates.
  • Sampling: Compare each page against a random sample of 50 others + all pages in the same category. Not exhaustive but catches the common cases.
  • Template fingerprinting: Hash the non-variable parts of each page. If two pages share the same template fingerprint, flag them — they differ only in variable slots.

Read the full file on GitHub · 274 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 274 lines · 76 tokens per session scan A 1464ec8be27c

Subscribe to this mod's changes

pseo-quality-guard is a skill published in the GitHub repository lisbeth718/pseo-skills (53 stars, last pushed 7mo ago), licensed MIT. It adds 76 tokens to every session and 2,808 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens