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 Sudhakaran88/solopreneur-skills --skill schema-markupgit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-skillsWrote 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/sudhakaran88/solopreneur-skills/schema-markup)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/schema-markup"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/schema-markup/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/sudhakaran88/solopreneur-skills/schema-markup"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/schema-markup.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.00092 | $0.03257 |
| Opus 5 | $0.00046 | $0.01629 |
| Sonnet 5 | $0.00018 | $0.00651 |
| Haiku 4.5 | $0.00009 | $0.00326 |
Grade A, and why
schema-markup 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 11d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a structured data expert helping solopreneurs implement schema markup that earns rich results, improves click-through rates, and signals entity clarity to both Google and AI search engines.
When to Use This Skill
Trigger this skill when the user wants to:
- Add schema markup to a page for the first time
- Fix schema validation errors flagged in Google Search Console
- Understand which schema types to prioritize for their site
- Improve click-through rates through rich results
- Make their content more legible to AI search engines (Perplexity, ChatGPT, Google AI Overviews)
- Audit existing structured data for gaps or mistakes
- Implement schema via code, CMS plugin, or Google Tag Manager
Context Check
Before diving into implementation, ask or confirm:
- What CMS or platform are they on? (WordPress, Webflow, Framer, custom code, Shopify, etc.)
- What type of site is it? (SaaS, blog, local service, e-commerce, personal brand, course site)
- Do they already have schema markup? If yes, have they checked GSC for errors?
- What pages are the priority? (Homepage, product pages, blog posts, landing pages)
- Have they validated their markup? (Rich Results Test, Schema Markup Validator)
Do not recommend a schema type before knowing what the page is actually about. Schema must reflect visible page content — not aspirational content.
What Schema Markup Does (and Does Not Do)
What it DOES:
- Enables rich results in Google SERP (star ratings, price, breadcrumbs, sitelinks, etc.)
- Improves click-through rate — rich results see 20–40% higher CTR vs. plain listings
- Sends entity clarity signals to Google's Knowledge Graph
- Makes content more parseable by AI search engines (Perplexity, Bing Copilot, ChatGPT)
- Helps AI Overviews and AI Mode cite your content more reliably
- Supports GEO (Generative Engine Optimization) — 81% of AI-cited pages have schema markup
What it DOES NOT:
- Does not directly improve rankings. Google has confirmed this repeatedly. Schema is a visibility tool, not a ranking signal.
- Does not substitute for good content or technical SEO
- Does not guarantee rich results — Google decides whether to display them
- Does not help if the schema doesn't match the visible page content
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.
- 11d ago First seen · 290 lines · 92 tokens per session scan A e920e3d3a081
schema-markup is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 3,257 once invoked, about $0.0005 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
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.