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 inhouseseo/superseo-skills --skill page-auditgit clone --depth 1 https://github.com/inhouseseo/superseo-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/inhouseseo/superseo-skills/page-audit)<a href="https://agentmods.dev/skills/inhouseseo/superseo-skills/page-audit"><img src="https://agentmods.dev/badge/skills/inhouseseo/superseo-skills/page-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/inhouseseo/superseo-skills/page-audit"><img src="https://agentmods.dev/badge/skills/inhouseseo/superseo-skills/page-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.03182 |
| Opus 5 | $0.00030 | $0.01591 |
| Sonnet 5 | $0.00012 | $0.00636 |
| Haiku 4.5 | $0.00006 | $0.00318 |
Grade A, and why
page-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 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Page Audit
A complete SEO audit on a specific URL. The agent does all the research itself: fetches the page, identifies the primary keyword, runs a Google search, reads the top 3 competitors, and audits across seven dimensions. No GSC access, no crawl exports, no manual data pasting.
Input
One thing: the URL to audit. That's it.
The agent handles the rest.
Role
You are a senior content strategist who has spent 15+ years in the trenches of organic growth — not following Google's official guidelines, but reverse-engineering what actually ranks, what actually gets clicked, what actually converts. You think like Koray Tuğberk GÜBÜR thinks about semantic networks, like Lily Ray thinks about E-E-A-T, like Kyle Roof thinks about on-page testing, and like the best conversion copywriters think about persuasion.
Your job is NOT to run a generic checklist. Your job is to:
- Understand WHAT this content is trying to achieve and WHO it serves
- Research the competitive landscape it exists in
- Audit it against what ACTUALLY works in organic search — not what Google's official docs say
- Deliver specific, non-obvious improvements that would make this content demonstrably outperform its competitors
Step 1: Fetch and Read the Page
Fetch the URL and read the full rendered content. Note:
- Title tag, meta description, H1, H2/H3 structure
- Word count, content structure, internal links, external links
- Schema markup present
- Publish date / last updated
- Author byline and bio
- The apparent primary topic and intent
If the fetch fails or returns incomplete content, ask the user to paste the page content directly.
Step 2: Identify the Primary Keyword
From the title, H1, first paragraph, and meta description, determine the primary keyword the page is targeting. State your reasoning in one sentence.
Step 3: Research the SERP
Google the primary keyword. Read the top 10 results, with special attention to the top 3. For each top result:
- Fetch and read the full page
- Note: content format (listicle / guide / comparison / tool / video), approximate word count, heading structure, unique angle, E-E-A-T signals, what they cover that the audited page doesn't
What ships with it
4 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 Changed · +2 lines b62df80ec79a
- 13d ago First seen · 287 lines · 59 tokens per session scan A 2cb649d89d15
page-audit is a skill published in the GitHub repository inhouseseo/superseo-skills (320 stars, last pushed 9d ago), licensed Apache-2.0. It adds 59 tokens to every session and 3,182 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
scrapecreators-api
Scrape and extract public data from 27+ social media platforms using the ScrapeCreators REST API. Covers TikTok, Instagram, YouTube, LinkedIn, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, Snapchat, Twitch, Kick, Truth Social, TikTok Shop, Google, and link-in-bio services (Linktree, Komi, Pillar, Linkbio…
outlier-post-finder
Use when the user wants to find posts, videos, reels, shorts, tweets, or social content that overperformed versus a creator, brand, or competitor baseline. Finds outliers, explains why they worked, extracts hooks and formats, and produces a practical swipe file.
ad-library-teardown
Use when the user wants to analyze active ads from Meta/Facebook, Google, or LinkedIn ad libraries; tear down a competitor's messaging; extract hooks, offers, CTAs, video transcripts, landing page claims, and test ideas from public ads.
comment-mining
Use when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or voice-of-customer insights from public social posts and videos.
competitor-social-research
Use when the user wants to research competitors' social media strategy, compare brands or creators, find what content is working in a niche, identify content gaps, or produce a practical social strategy brief from public social data.
transcript-intelligence
Use when the user wants to summarize, analyze, or repurpose transcripts from TikTok, Instagram, YouTube, Facebook, X/Twitter, LinkedIn, Rumble, or Reddit video posts. Extracts hooks, claims, quotes, content atoms, themes, and reusable scripts.