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 thisisAhsanIqbal/nextjs-seo-audit --skill schema-json-optimizationgit clone --depth 1 https://github.com/thisisAhsanIqbal/nextjs-seo-auditWrote 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/thisisahsaniqbal/nextjs-seo-audit/schema-json-optimization)<a href="https://agentmods.dev/skills/thisisahsaniqbal/nextjs-seo-audit/schema-json-optimization"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/schema-json-optimization/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/thisisahsaniqbal/nextjs-seo-audit/schema-json-optimization"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/schema-json-optimization.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.01202 |
| Opus 5 | $0.00028 | $0.00601 |
| Sonnet 5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
schema-json-optimization 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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema JSON Optimization
Validate existing JSON-LD and suggest only relevant schemas based on the detected page type.
Important: Do NOT blindly check for all schema types. First detect what kind of page this is, then only validate/suggest schemas that are applicable.
Step 1: Find and validate existing JSON-LD
Look for all <script type="application/ld+json"> elements:
- None found → ⚠️ WARN "No JSON-LD schema markup found"
- Found → ✅ PASS "Found N JSON-LD block(s)" → validate each:
Validation rules
- Invalid JSON → ❌ FAIL "Could not parse JSON-LD"
- Missing
@context→ ❌ FAIL - Missing
@type→ ❌ FAIL - Valid → ✅ PASS and check type-specific required fields (see Step 3)
Step 2: Auto-detect page type
Scan the HTML for signals to determine what type of page this is. A page may match zero, one, or multiple types:
| Page type | Detection signals |
|---|---|
| Article / Blog | <meta property="article:published_time">, <article> tag, blog-like URL patterns (/blog/, /post/, /news/) |
| LocalBusiness | <address> tag, <a href="tel:...">, [itemprop="telephone"], [itemprop="address"], contact page patterns |
| Product | <meta property="og:type" content="product">, price elements ([itemprop="price"]), add-to-cart buttons |
| FAQ | Multiple <details>/<summary> or FAQ-patterned heading + paragraph pairs |
| Organization | About page with company info, <meta property="og:type" content="website"> on homepage |
| BreadcrumbList | <nav aria-label="breadcrumb">, .breadcrumb class, <ol> with breadcrumb-like links |
| WebSite | Homepage with site-wide search form |
If no type is detected → only validate existing schemas, do not suggest new ones.
Step 3: Validate and suggest ONLY for detected types
Only if Article/Blog detected:
Check existing Article schema for:
| Field | Missing = |
|---|---|
headline |
⚠️ WARN |
datePublished |
⚠️ WARN |
author |
⚠️ WARN |
image |
⚠️ WARN |
description |
⚠️ WARN |
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.
- 9d ago First seen · 138 lines · 56 tokens per session scan A 6769d83e3990
schema-json-optimization is a skill published in the GitHub repository thisisAhsanIqbal/nextjs-seo-audit (7 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 1,202 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-31.
Other skills, from other repositories
wgm
Autonomous build skill that turns a rough request into working software through a relentless requirements interview (grill), a persistent plan, and a Ralph-style build loop (analyze → implement → validate → review → record). Use when the user runs /wgm, or asks to build, implement, prototype, or ship a feature or app…
rugged
Companion review skill that stress-tests a request, spec, plan, diff, or system against the operators and environment that will actually run it, not an idealized one. Runs a disciplined lifecycle (Triage -> Context -> Bottleneck decomposition -> Simplify -> Field test -> Verdict) and emits exactly one of three…
teach-me
Companion learning skill that makes a codebase legible fast. Surveys a repository, builds a cited map, runs a guided tour in dependency order, and finishes with a validated first change so the learner has actually moved the code. Use when the user runs /teach-me, or asks to learn, understand, onboard onto, get up to…
podlite-markup
Create and edit Podlite markup files. Use when working with .podlite files, or when the user mentions Podlite, formatting codes, declarative blocks, structured markup for documentation, or AI agent instructions.
podlite-verify
Validate, lint, and self-check Podlite markup. Use after generating or editing .podlite files, when asked to verify/validate/lint/check Podlite, or to catch structural errors (unbalanced =begin/=end, attribute syntax, nested angles, list nesting) before delivering output.
quiz-me
Companion assessment skill that grills a user on a codebase until their understanding is proven rather than assumed. Asks one question at a time, grades every answer against the real code with citations, scores 0-100 by difficulty tier, and drills the weak areas it finds. Use when the user runs /quiz-me, or asks to be…