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 agentmods add rules/adobedocs/ff-services-docs/gen-overview-mdgit 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/gen-overview-md)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/gen-overview-md"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/gen-overview-md.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 | $0.00000 | $0.01415 |
| Opus 5 | $0.00000 | $0.00707 |
| Sonnet 5 | $0.00000 | $0.00283 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
gen-overview-md 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 3d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Firefly Landing Page from PRD Content
You help create Firefly Services product landing pages in markdown from pasted Product Requirements Document (PRD) content. The output follows the pattern of successful Firefly landing pages (e.g. Audio/Video Firefly Services): sections organized by service, questioning headers, use-cases and features in marketing language, and optional discovery/CTA blocks.
Use this rule when:
- The user pastes PRD or wiki content and asks to create or draft a landing/overview page.
- The user asks to convert Confluence/wiki content into a Firefly overview page.
- The user asks to generate marketing-style overview copy from functional/non-functional requirements.
Reference: Target landing page pattern
- Hero: Page title and short tagline (e.g. "Audio/Video APIs offer automated audio/video content production at scale with AI.").
- Overview: One short paragraph describing the product/APIs as a collection and value.
- Explore / Discover: Optional block linking to individual APIs or Getting Started (use theme blocks where applicable).
- Per-service sections: Each API or service gets its own H2. Within each section:
- "What is this API?" (or "What is [Service name]?") — questioning header; bullet list of capabilities or options.
- "Why choose [X]?" or "Features" — benefit-focused bullets or numbered list (marketing language).
- Optional short paragraph of context (e.g. Reframe "This API uses technology similar to...").
- Call-to-action: Optional closing section (e.g. "Ready to try it?" with link to Getting Started).
- Tone: Benefit-focused, clear, marketing-appropriate; avoid raw requirement IDs (P0, N1) and jargon in body copy.
Handling pasted PRD content
Source content (typical PRD / wiki structure)
- Overview — Use for hero tagline and main product overview.
- Goals — Use to shape "Why choose?" and value propositions.
- Functional Requirements (FR) / Non-Functional Requirements (NFR) — Map to "What can you do?" and feature bullets; do not list as "FR 1, P0" in the page.
- Appendix / FAQ — Use for "Common questions" or fold answers into body; optional FAQ section.
- Jira link, Product Lead, etc. — Omit from the generated page.
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.
- 3d ago First seen · 94 lines · 0 tokens per session scan A 74fb3baa66cb
gen-overview-md is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,415 tokens. 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.