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/thatrebeccarae/claude-marketingWrote 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/rules/thatrebeccarae/claude-marketing/schema-markup-generator)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/schema-markup-generator"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/schema-markup-generator.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.00075 | $0.01633 |
| Opus 5 | $0.00037 | $0.00816 |
| Sonnet 5 | $0.00015 | $0.00327 |
| Haiku 4.5 | $0.00007 | $0.00163 |
Grade A, and why
schema-markup-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 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Markup Generator
Generate JSON-LD structured data for rich results, AI citations, and enhanced search visibility.
When to Use
- Adding structured data to new or existing pages
- Generating JSON-LD for specific schema types
- Auditing existing schema for errors or missing fields
- Improving AI search visibility (pairs with aeo-geo-optimizer)
- Enabling rich results (FAQ dropdowns, star ratings, how-to steps)
Workflow
Step 1: Identify Content Type
| Content | Primary Schema | Rich Result |
|---|---|---|
| Blog post | Article | Enhanced listing with author, date |
| FAQ section | FAQPage | Expandable Q&A in SERPs |
| Tutorial | HowTo | Step-by-step with images/time |
| Product page | Product | Price, availability, ratings |
| Review | Review + Rating | Star ratings in SERPs |
| Recipe | Recipe | Cooking time, ingredients, ratings |
| Event | Event | Date, location, ticket info |
| Local business | LocalBusiness | Maps, hours, contact |
| Person/author | Person | Knowledge panel |
| Breadcrumbs | BreadcrumbList | Breadcrumb trail in SERPs |
| Video | VideoObject | Video carousel, thumbnails |
| Software | SoftwareApplication | App info in SERPs |
| Course | Course | Course info in SERPs |
| Dataset | Dataset | Dataset search results |
Step 2: Generate JSON-LD
Generate a <script type="application/ld+json"> block with all required and recommended fields for the schema type. Always use JSON-LD format (not Microdata or RDFa).
Step 3: Validate
- Google Rich Results Test: https://search.google.com/test/rich-results
- Schema.org Validator: https://validator.schema.org/
- Check Google Search Console for structured data errors
Schema Templates
Article
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article Title (max 110 chars)",
"description": "Brief description of the article",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://example.com/author/name",
"jobTitle": "Author Title",
"sameAs": ["https://linkedin.com/in/author", "https://twitter.com/author"]
},
"publisher": {
"@type": "Organization",
"name": "Publisher Name",
"logo": {"@type": "ImageObject", "url": "https://example.com/logo.png"}
},
"datePublished": "2026-03-18T00:00:00Z",
"dateModified": "2026-03-18T00:00:00Z",
"image": "https://example.com/article-image.jpg",
"mainEntityOfPage": {"@type": "WebPage", "@id": "https://example.com/article-url"}
}
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 · 194 lines · 75 tokens per session scan A 14e3fa7beb89
schema-markup-generator is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (132 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 1,633 once invoked, about $0.0004 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.