Borrowing it
Nothing to install: this file belongs to littlebearapps/pitchdocs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/littlebearapps/pitchdocs/main/.cursorrulesgit clone --depth 1 https://github.com/littlebearapps/pitchdocsWrote 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/littlebearapps/pitchdocs/cursorrules)<a href="https://agentmods.dev/rules/littlebearapps/pitchdocs/cursorrules"><img src="https://agentmods.dev/badge/rules/littlebearapps/pitchdocs/cursorrules/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/littlebearapps/pitchdocs/cursorrules"><img src="https://agentmods.dev/badge/rules/littlebearapps/pitchdocs/cursorrules.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.00642 | $0.00642 |
| Opus 5.5 | $0.00257 | $0.00257 |
| Sonnet 5.5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
cursorrules 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PitchDocs — Cursor Rules
You are working on PitchDocs, a Claude Code plugin that generates marketing-quality repository documentation. This is a pure Markdown project with no code runtime.
Architecture
- Skills (16):
.claude/skills/*/SKILL.md— reference knowledge loaded on-demand - Agents (4):
.claude/agents/*.md— docs-writer (orchestrator), docs-researcher, docs-reviewer;agents/docs-freshness.md— installed per-project by/pitchdocs:activate - Rules (3 auto-loaded + 2 installable):
.claude/rules/content-filter.md(global);.claude/rules/doc-standards.md,.claude/rules/docs-awareness.md(installed auto-loaded);rules/doc-standards.md,rules/docs-awareness.md(source templates installed per-project by/pitchdocs:activate) - Commands (16):
commands/*.md— 14 active + 2 stubs redirecting to ContextDocs - Hooks (1 opt-in):
hooks/content-filter-guard.sh— installed per-project by/pitchdocs:activate install strict(Claude Code only)
Writing Standards
- Australian English (realise, colour, behaviour, licence/license)
- Benefit-driven language:
[Feature] so you can [outcome] — [evidence](with optional JTBD job mapping for richer benefits) - 4-question test on every doc: problem solved? usable? credible? linked?
- Progressive disclosure: non-technical first, technical deeper
- Every feature claim must trace to actual code (file path, function, config)
File Sync Requirements
When adding skills or commands, update all of:
README.md(commands table, features section)AGENTS.md(skills table, commands table, if applicable)llms.txt(file reference with benefit description).github/ISSUE_TEMPLATE/bug_report.yml(component dropdown)
Protected Files
docs/faq/index.md is load-bearing — it sources the marketing-site FAQPage JSON-LD on https://littlebearapps.com/help/pitchdocs/. The docs-sync pipeline (scripts/docs-sync.config.ts in littlebearapps/littlebearapps.com, mapped under pitchdocs with category: faq) hard-fails if the directory is missing. Keep ≥7 question-shaped H2 headings (##); edit entries in place; never delete. See Protected Documentation Files in AGENTS.md.
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 · 40 lines · 642 tokens per session scan A fcd13e8bfcbc
cursorrules is a cursor rule published in the GitHub repository littlebearapps/pitchdocs (8 stars, last pushed 5mo ago), licensed MIT. It adds 642 tokens to every session, about $0.0026 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).