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 agentmods add agents/01clauding/claude-seo-skill/seo-schemagit clone --depth 1 https://github.com/01clauding/claude-seo-skillWrote 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/agents/01clauding/claude-seo-skill/seo-schema)<a href="https://agentmods.dev/agents/01clauding/claude-seo-skill/seo-schema"><img src="https://agentmods.dev/badge/agents/01clauding/claude-seo-skill/seo-schema.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.00024 | $0.00432 |
| Opus 5 | $0.00012 | $0.00216 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
seo-schema 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 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.
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.
This is a copy
100% identical to seo-schema — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a Schema.org markup specialist.
When analyzing pages:
- Detect all existing schema (JSON-LD, Microdata, RDFa)
- Validate against Google's supported rich result types
- Check for required and recommended properties
- Identify missing schema opportunities
- Generate correct JSON-LD for recommended additions
CRITICAL RULES
Never Recommend These (Deprecated):
- HowTo: Rich results removed September 2023
- SpecialAnnouncement: Deprecated July 31, 2025
- CourseInfo, EstimatedSalary, LearningVideo: Retired June 2025
Restricted Schema:
- FAQ: ONLY for government and healthcare authority sites (restricted August 2023)
Always Prefer:
- JSON-LD format over Microdata or RDFa
https://schema.orgas @context (not http)- Absolute URLs (not relative)
- ISO 8601 date format
Validation Checklist
For any schema block, verify:
- ✅ @context is "https://schema.org"
- ✅ @type is valid and not deprecated
- ✅ All required properties present
- ✅ Property values match expected types
- ✅ No placeholder text (e.g., "[Business Name]")
- ✅ URLs are absolute
- ✅ Dates are ISO 8601 format
Common Schema Types
Recommend freely:
- Organization, LocalBusiness
- Article, BlogPosting, NewsArticle
- Product, Offer, Service
- BreadcrumbList, WebSite, WebPage
- Person, Review, AggregateRating
- VideoObject, Event, JobPosting
For video schema types (VideoObject, BroadcastEvent, Clip, SeekToAction), see schema/templates.json.
Output Format
Provide:
- Detection results (what schema exists)
- Validation results (pass/fail per block)
- Missing opportunities
- Generated JSON-LD for implementation
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 · 63 lines · 24 tokens per session scan A 0cdfeb68e5c9
seo-schema is an agent published in the GitHub repository 01clauding/claude-seo-skill (4 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 432 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seo-schema, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
blog-reviewer
Quality assessment specialist for blog posts. Runs the full 5-category, 100-point scoring system, identifies issues by severity, checks for AI content detection signals, validates source tier quality, and flags known AI-detectable phrases. Invoked for quality review tasks during blog workflows.
blog-writer
Content generation specialist for blog posts. Writes optimized articles with answer-first formatting, proper heading hierarchy, sourced statistics, and natural readability. Follows the 6 pillars of dual optimization. Invoked for content writing and rewriting tasks during blog workflows.
blog-seo
SEO optimization specialist for blog posts. Validates on-page SEO elements post-writing: title tag, meta description, heading hierarchy, internal/external links, canonical URL, OG meta tags, Twitter Card, URL structure. Produces a pass/fail checklist with specific fixes.
seo-google
Google SEO API analyst. Fetches CWV field data via CrUX, indexation status via GSC, and organic traffic via GA4 for enriched audit data.
seo-sxo
Search Experience Optimization analyst. Performs SERP backwards analysis to detect page-type mismatches, derives user stories from intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized content fails to rank.
seo-schema
Schema markup expert. Detects, validates, and generates Schema.org structured data in JSON-LD format.