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 pseo-auditgit 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/pseo-audit)<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-audit"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-audit.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.00062 | $0.01020 |
| Opus 5 | $0.00031 | $0.00510 |
| Sonnet 5 | $0.00012 | $0.00204 |
| Haiku 4.5 | $0.00006 | $0.00102 |
Grade A, and why
pseo-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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pSEO Codebase Audit
Perform a structured audit of the codebase to assess readiness for programmatic SEO at 1000+ page scale. Produce a concrete gap analysis with actionable findings.
If pseo-discovery was run first, use its output to focus the audit: check whether the codebase can support the specific page types, data models, and URL structures the discovery proposed. If discovery was not run, audit generically.
Audit Procedure
1. Identify the Framework and Architecture
- Detect the framework (Next.js, Astro, Nuxt, Remix, etc.) from config files
- Identify the rendering strategy: SSG, SSR, ISR, or client-side
- Map the routing structure: file-based, dynamic segments, catch-all routes
- Check for
generateStaticParams,getStaticPaths, or equivalent
2. Assess Data Architecture
- Locate data sources: CMS, database, API, local files (JSON, MDX, CSV)
- Check for a centralized data-fetching layer vs. scattered inline fetches
- Evaluate whether data models have the fields needed for SEO (title, description, slug, category, FAQ, etc.)
- Look for a slug/URL generation strategy and whether it enforces uniqueness
3. Evaluate Routing and Page Templates
- Count dynamic route segments and template pages
- Check if templates produce unique content per page or rely on the same copy with minor variable swaps
- Look for catch-all routes that may create orphan or thin pages
- Verify 404 handling for invalid slugs
4. Review SEO Foundations
- Check for dynamic metadata generation (title, description, canonical)
- Look for Open Graph and Twitter card tags
- Search for JSON-LD structured data or schema markup
- Check for a sitemap generator (static or dynamic)
- Look for robots.txt configuration
- Verify canonical URLs are set and self-referencing by default
5. Evaluate Internal Linking
- Look for breadcrumb components
- Search for related-pages or hub-spoke linking patterns
- Check for programmatic cross-linking between pages
- Assess whether link structures create topical clusters
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.
- 7d ago First seen · 127 lines · 62 tokens per session scan A b07ee59a859a
pseo-audit is a skill published in the GitHub repository lisbeth718/pseo-skills (53 stars, last pushed 7mo ago), licensed MIT. It adds 62 tokens to every session and 1,020 once invoked, about $0.0003 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…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…