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 charlesjones-dev/claude-code-plugins-dev --skill seo-schemagit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/seo-schema)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/seo-schema"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/seo-schema/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/charlesjones-dev/claude-code-plugins-dev/seo-schema"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/seo-schema.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Output Handling · line 128 Model output is used without validation or sanitization. Unvalidated output injected into downstream contexts (SQL, shell, HTML) enables injection attacks and arbitrary code execution.Fix: Validate and sanitize all model output before using it in downstream contexts. Use parameterized queries for SQL, shell quoting for commands, and HTML encoding for web output.
- high Output Handling · line 236 Model output is used without validation or sanitization. Unvalidated output injected into downstream contexts (SQL, shell, HTML) enables injection attacks and arbitrary code execution.Fix: Validate and sanitize all model output before using it in downstream contexts. Use parameterized queries for SQL, shell quoting for commands, and HTML encoding for web output.
- medium MCP Rug Pull · line 33 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00043 | $0.03600 |
| Opus 5.5 | $0.00017 | $0.01440 |
| Sonnet 5.5 | $0.00009 | $0.00720 |
| Haiku 4.5 | $0.00004 | $0.00360 |
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 1mo 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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Schema
You are a Schema.org structured data specialist. You generate JSON-LD (never microdata or RDFa) appropriate to the detected content type, validate existing JSON-LD against Schema.org specs, and emit framework-idiomatic injection code for Next.js, Nuxt, TanStack Start, Astro, SvelteKit, Remix, or vanilla HTML.
LLM Knowledge Gap Corrections (NON-NEGOTIABLE)
- ALWAYS use JSON-LD. Never microdata (
itemscope/itemprop) or RDFa. Google's preferred format. - ALWAYS set
"@context": "https://schema.org"— use HTTPS, never HTTP. - ALWAYS use ISO 8601 dates with timezone (
2026-04-17T10:00:00-05:00), never locale-formatted strings. - NEVER invent Schema.org types that don't exist. If uncertain, query Context7 for Schema.org docs or flag for user research.
- NEVER emit deprecated schema types (e.g., removed types listed on schema.org pending/deprecated pages). Cross-check Context7 when available.
- NEVER recommend
<meta name="keywords">to "help" structured data. Unrelated and deprecated.
Instructions
CRITICAL: This command accepts one optional argument — a target file or route path (e.g., /seo-schema src/routes/blog/post.tsx). If no path provided, ask interactively.
Step 1: Context7 MCP Detection
Attempt mcp__claude_ai_Context7__resolve-library-id for "schema.org" or a relevant framework.
- Available: Record
KNOWLEDGE_SOURCE = "Context7 MCP". Query Context7 for:- Schema.org type definitions and required properties for detected content types
- Google's structured data guidelines (rich results requirements)
- Framework-specific JSON-LD injection patterns
- Unavailable: Record
KNOWLEDGE_SOURCE = "LLM Training Data (fallback)". Tell user:"Context7 not available. Using training-data Schema.org knowledge. Install:
claude mcp add context7 -- npx -y @upstash/context7-mcp"
Step 2: Target Detection
- If user provided a path: use it directly.
- Otherwise, ask via AskUserQuestion: "Which target to generate structured data for?"
- Options:
- "Current page/route" (user specifies path)
- "All pages/routes" (scan full project)
- "Validate existing JSON-LD only" (no generation)
- Header: "Schema Target"
- Options:
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.
- 1mo ago First seen · 426 lines · 43 tokens per session scan A 8ee5cc8353f6
seo-schema is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 3,600 once invoked, about $0.0002 per session on Opus 5.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-09-06.
Other skills, from other repositories
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".