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/ProductBuilders/productbuildersWrote 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/productbuilders/productbuilders/seo-llmo-integration)<a href="https://agentmods.dev/rules/productbuilders/productbuilders/seo-llmo-integration"><img src="https://agentmods.dev/badge/rules/productbuilders/productbuilders/seo-llmo-integration/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/rules/productbuilders/productbuilders/seo-llmo-integration"><img src="https://agentmods.dev/badge/rules/productbuilders/productbuilders/seo-llmo-integration.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.00006 | $0.01331 |
| Opus 5.5 | $0.00002 | $0.00532 |
| Sonnet 5.5 | $0.00001 | $0.00266 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade A, and why
seo-llmo-integration 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 2mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rule: Universal SEO and LLMO (OpenAI/ChatGPT) Integration
1. SEO Requirements
a. Sitemap
- Add or update
public/sitemap.xmlto include all main pages, project detail pages, and important URLs. - Each
<url>should have<loc>,<lastmod>,<changefreq>, and<priority>. - Example:
<url> <loc>https://yourdomain.com/page</loc> <lastmod>2025-05-15</lastmod> <changefreq>monthly</changefreq> <priority>0.8</priority> </url>
b. Robots.txt
- Ensure
public/robots.txtreferences the sitemap and allows major crawlers. - Example:
User-agent: * Allow: / Sitemap: https://yourdomain.com/sitemap.xml
c. Meta Tags
- Use dynamic meta tags for each page (title, description, canonical, Open Graph, Twitter Card).
- Implement with a reusable component (e.g.,
MetaTags.tsx). - Example:
<title>Page Title | Site Name</title> <meta name="description" content="Page summary." /> <link rel="canonical" href="https://yourdomain.com/page" /> <meta property="og:title" content="Page Title" /> <meta property="og:description" content="Page summary." /> <meta property="og:url" content="https://yourdomain.com/page" /> <meta name="twitter:card" content="summary_large_image" />
d. Structured Data (JSON-LD)
- Add or update
public/structured-data.jsto inject JSON-LD schemas for key entities (e.g., Person, Project, Article, SoftwareApplication). - Example:
{ "@context": "https://schema.org", "@type": "CreativeWork", "name": "Project Title", "description": "Short description of project" }
e. Accessibility & Best Practices
- Ensure all images have
altattributes. - Use semantic HTML and ARIA labels where appropriate.
- Ensure good heading structure and color contrast.
2. LLMO/AI (OpenAI, ChatGPT Plugin) Integration
a. API Endpoints
- Expose relevant data (projects, articles, etc.) via RESTful endpoints (e.g.,
/api/projects.json). - Responses should be structured, machine-readable, and include all relevant fields.
- Example:
[ { "id": "project-id", "title": "Project Title", "description": "Summary...", ... } ]
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.
- 2mo ago First seen · 170 lines · 6 tokens per session scan A 050f2e0ec98f
seo-llmo-integration is a cursor rule published in the GitHub repository ProductBuilders/productbuilders (10 stars, last pushed 1y ago), licensed MIT. It adds 6 tokens to every session and 1,331 once invoked, about $0.0000 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-08-31.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).