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/AdobeDocs/ff-services-docsWrote 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/adobedocs/ff-services-docs/cursor-rules)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/cursor-rules"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/cursor-rules/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/adobedocs/ff-services-docs/cursor-rules"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/cursor-rules.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.00666 | $0.00666 |
| Opus 5.5 | $0.00266 | $0.00266 |
| Sonnet 5.5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
cursor-rules 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rules Location
Purpose: define how to create new Cursor rules in this repo.
Quick checklist (LLM)
- File lives in
PROJECT_ROOT/.cursor/rules/ - Filename is kebab-case and ends with
.mdc - Frontmatter contains
description,globs(optional),alwaysApply - Rule has a clear title and concise instructions
Where rules live
Always place rule files in PROJECT_ROOT/.cursor/rules/:
.cursor/rules/
├── your-rule-name.mdc
├── another-rule.mdc
└── ...
Never place rule files:
- In the project root
- In subdirectories outside
.cursor/rules - In any other location
Project Agent skills (optional)
Rules (this folder) are always-on or glob-scoped instructions for the agent. Skills live under PROJECT_ROOT/.cursor/skills/<skill-name>/SKILL.md and describe fuller workflows (for example stage-all-and-commit). If you add a skill, consider a short companion rule or a line in this file so contributors know it exists.
- Git:
/gc·/gcam— .cursor/rules/gc-commit-skill.mdc, .cursor/skills/gc/SKILL.md, .cursor/skills/gcam/SKILL.md - OpenAPI JSON (
static/):/api-eval·/api-review·/api-fix— .cursor/rules/api-ref-skills.mdc; agent .cursor/agents/api-spec-reviewer.md
Naming conventions
- Use kebab-case for filenames
- Always use
.mdcextension - Make names descriptive of the rule's purpose
Rule file template
Each rule file follows this structure:
Metadata section
---
description: Short description of the rule's purpose
globs: optional/path/pattern/**/*
alwaysApply: false
---
# Rule Title
Main content explaining the rule with markdown formatting and establishing the context for the rule use-case.
Include a numbered list of use cases or functions the rule is intended to perform so users understand the agent's purpose and how to use it.
## Contents section
Organize concepts with headings and subheadings in this order:
1. Step-by-step instructions
2. Code examples
3. Guidelines
Example:
```typescript
// Good example
function goodExample() {
// Implementation following guidelines
}
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 · 92 lines · 666 tokens per session scan A 38a2be14ac0c
cursor-rules is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 666 tokens to every session, about $0.0027 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).