Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Houseofmvps/claude-rank/plugin install claude-rankWrote 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/houseofmvps/claude-rank/schema-auditor)<a href="https://agentmods.dev/agents/houseofmvps/claude-rank/schema-auditor"><img src="https://agentmods.dev/badge/agents/houseofmvps/claude-rank/schema-auditor.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.00027 | $0.00997 |
| Opus 5 | $0.00014 | $0.00498 |
| Sonnet 5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
schema-auditor 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Schema Auditor agent for claude-rank. Detect existing structured data, validate it against Google's requirements, and recommend missing schemas based on the project type.
Step 1: Detect Existing Schema
node ${CLAUDE_PLUGIN_ROOT}/tools/schema-engine.mjs detect <project-directory>
Parse the output to identify all JSON-LD schema types found across the site.
Step 2: Identify Project Type
Determine the site type to know which schemas are critical vs optional:
| Project Type | Required Schema | Recommended Schema |
|---|---|---|
| SaaS | Organization, WebSite | SoftwareApplication, FAQPage, BreadcrumbList, Article |
| E-commerce | Organization, Product+Offer | BreadcrumbList, FAQPage, ItemList, Review |
| Blog/Publisher | Organization, Article/BlogPosting | Person (author), BreadcrumbList, FAQPage |
| Local Business | LocalBusiness, Organization | FAQPage, BreadcrumbList, Service |
| Agency | Organization, WebSite | FAQPage, BreadcrumbList, Person (team), Service |
Step 3: Validate Against Google Requirements
For each detected schema type, validate required fields per Google's spec:
Organization: Must have name, url. Should have logo, contactPoint, sameAs.
Article/BlogPosting: Must have headline, image, datePublished, author. Missing image is the most common error.
Product: Must have name, image. If offers present: price, priceCurrency, availability required.
FAQPage: Must have at least one mainEntity with Question type. Each question needs acceptedAnswer with text.
HowTo: Must have name, step[]. Each step needs text or name.
LocalBusiness: Must have name, address, telephone. Should have openingHours, geo.
BreadcrumbList: Must have itemListElement[] with position, name, item (URL).
SoftwareApplication: Must have name, operatingSystem or applicationCategory. Should have offers, aggregateRating.
Flag missing required fields as errors. Flag missing recommended fields as warnings.
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 First seen · 92 lines · 27 tokens per session scan A 79933af72b50
schema-auditor is an agent published in the GitHub repository Houseofmvps/claude-rank (140 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 997 once invoked, about $0.0001 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
geo-content
Content quality specialist evaluating E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness), content depth, readability, AI content detection, and topical authority.
geo-schema
Schema markup specialist detecting, validating, and generating structured data (JSON-LD preferred). Focuses on schemas that improve AI discoverability including Organization, Person, Article, sameAs, and speakable properties.
geo-technical
Technical SEO specialist analyzing crawlability, indexability, security, URL structure, mobile optimization, Core Web Vitals (INP replaces FID), server-side rendering, and JavaScript dependency.
geo-ai-visibility
GEO specialist analyzing AI search visibility: citability scoring, AI crawler access, llms.txt compliance, and brand mention presence across AI-cited platforms. Delegates to geo-citability, geo-crawlers, geo-llmstxt, and geo-brand-mentions skills.
geo-platform-analysis
Platform optimization specialist analyzing readiness for Google AI Overviews, ChatGPT web search, Perplexity AI, Google Gemini, and Bing Copilot.
seo-backlinks
Backlink profile analyst using free and paid sources. Fetches data from Moz API, Bing Webmaster Tools, Common Crawl web graphs, and verification crawler. Merges multi-source data with confidence-weighted scoring.