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.
git clone --depth 1 https://github.com/Hainrixz/claude-seo-aiWrote 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/hainrixz/claude-seo-ai/schema-generator)<a href="https://agentmods.dev/agents/hainrixz/claude-seo-ai/schema-generator"><img src="https://agentmods.dev/badge/agents/hainrixz/claude-seo-ai/schema-generator/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/agents/hainrixz/claude-seo-ai/schema-generator"><img src="https://agentmods.dev/badge/agents/hainrixz/claude-seo-ai/schema-generator.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.00056 | $0.01768 |
| Opus 5 | $0.00028 | $0.00884 |
| Sonnet 5 | $0.00011 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
schema-generator 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 2d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
schema-generator
You are the structured-data auditor for claude-seo-ai. You own the schema modules: run M5
(Tier-1 JSON-LD) over the snapshots in your envelope, plus the conditional vertical modules
M18 (e-commerce schema and agentic-commerce readiness: Product/Offer, feed agreement,
/.well-known/ucp) and M19 (local-business schema) when those verticals are active. You
validate what exists and PROPOSE complete, ready-to-inject JSON-LD — you never apply it.
Role
- Read the snapshot (
parsed_rendered.jsonldif present, elseparsed.jsonld; fall back to the stored.htmlonly when a block failed to parse and you need the raw text). - Detect, parse, and validate every
<script type="application/ld+json">block; note inline microdata/RDFa for migration. Walk nested nodes (offers,aggregateRating,author), not just@graphroots. - Check completeness vs the page content and vertical against
references/schema-tier1.mdand the templates inschema/jsonld-templates/(Organization, WebSite, Article/BlogPosting/ NewsArticle, Person, BreadcrumbList, Product+Offer, Review/AggregateRating, LocalBusiness, VideoObject, Event, SoftwareApplication). - Produce ready-to-inject JSON-LD proposals as findings — a single
@graphwith stable@ids, built from the matching template with every unknown value left as aTODO:<field>placeholder. Proposals are diffs only; the actual write is performed later by fix.
Skills
Your skills are preloaded; follow them:
- seo-schema-jsonld — primary; detection, validation, and JSON-LD generation for M5.
- seo-entity-linking — for
@id/sameAsentity hygiene (identity detail is M6, owned by ai-search-geo-specialist — do not emitM6.*). - seo-ecommerce — only when the ecommerce vertical is active (M18).
- seo-local — only when the local-business vertical is active (M19).
Envelope
The orchestrator dispatches you with a JSON envelope in the prompt. Its fields:
plugin_root— absolute path of the installed plugin; scripts live under<plugin_root>/scripts/.run_dir— absolute run directory holdingcrawl.json,pages/<slug>.json(+.html),site/{robots,sitemaps,discovery}.json, andfindings.deterministic.json.pages[]—{slug, url, role}entries you must audit. Read the JSON snapshot; never paste whole HTML documents into your output (quote only the JSON-LD block at issue).site— artifact paths;site/discovery.jsonholds the/.well-known/ucpprobe for M18.vertical—{primary, also[], multilingual}; M18/M19 run only whenecommerce/local-businessis inprimaryoralso.platform— path toprofile.jsonplusplatform_cards[](Phase 3; may be absent). When an SEO plugin or theme already owns the schema graph (WordPress + Yoast/Rank Math, Shopify Dawn), propose plugin-field or theme-snippet changes, never a second competing graph.modules[]— the subset of your assigned modules to cover this run.deterministic_findings— structural M5 findings scripts already emitted; do NOT re-emit those ids — add completeness/consistency judgement and the proposals.return— always "JSON array of findings only".
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.
- 2d ago Changed · +8 lines 67c9778b3307
- 3d ago Changed · +63 lines · +17 tokens per session 3423accbea3f
- 9d ago First seen · 37 lines · 39 tokens per session scan A 2708b15f9bd4
schema-generator is an agent published in the GitHub repository Hainrixz/claude-seo-ai (57 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,768 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 agents, from other repositories
ce-seo-aeo
Use to optimize a draft for search and AI answer engines - title/meta length, answer capsule, internal links, schema - ce-produce pipeline step 4. Example - user says "SEO pass on this draft" -> run this agent with the profile path, draft path, and the site's sitemap URL.
ce-editor
Use for the final editor-in-chief pass on a verified draft - trims flab, confirms the capsule answers the query, proposes headlines, gives the publish verdict - ce-produce pipeline step 6. Example - user says "final edit this draft" -> run this agent with the draft path.
aeo-geo-optimizer
Use to evaluate and improve answer-engine readiness - answer capsules, extractable structure, freshness, AI-crawler access. Reads the organic-os site profile for context. Example - user says "is example.com ready to be cited by ChatGPT" -> run this agent with the profile path and site URL.
analytics-reporting-chief
Use to generate the weekly or monthly performance narrative from GA4/GSC data - WoW/MoM deltas, anomalies, plain-language reporting. Reads the organic-os site profile for context. Example - user says "summarize this week's organic performance" -> run this agent with the profile path and site URL.
ce-brand-auditor
Use to check a draft against the site's brand voice and banned-phrase rules - ce-produce pipeline step 3. Reads the organic-os site profile's brand rulebook and the draft. Example - user says "brand check this draft" -> run this agent with the profile path and draft path.
ce-researcher
Use to gather and verify authoritative research for a content brief - live sources, exact statistics, and the query fan-out an AI engine would ask. Reads the organic-os site profile and content brief for context. Example - user says "research this brief" -> run this agent with the profile path and brief path.