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/api-ref-ffs-styleguidegit clone --depth 1 https://github.com/AdobeDocs/ff-services-docsWhat 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.00597 |
| Opus 5 | $0.00000 | $0.00298 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
api-ref-ffs-styleguide 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 2d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firefly Services API Style Guide (eval only)
Wiki: Firefly Services API Style Guide
Use with /api-eval only. /api-fix does not apply these unless Redocly flags them.
Offline checklist: .cursor/skills/api-eval/ffs-styleguide-checklist.md
Scope
Stateless Firefly Services RPC APIs. POST → async; GET (collections, status) → sync.
HTTP and URLs
- POST operations: async 202 pattern.
- URL shape:
https://{subdomain}.adobe.io/v{version}/{operation-name}. - POST paths: verb-led, hyphenated (e.g.
/v2/generate-object-composite). - GET collections: plural nouns.
Async 202 response
Required: jobId, statusUrl. Optional: cancelUrl. URLs: …/v{version}/status/{jobId}.
Status polling (GET)
status:not_started,running,succeeded,failed,partially_succeeded,canceled.jobIdon all status responses.- Failed:
error_codeorerrors[]per Error Codes wiki.
Errors
- 4xx/5xx and job failures:
error_coderequired;messageoptional. - Codes from Error Codes wiki.
JSON conventions
- Property names: camelCase (except
error_code). - American English spellings.
- Suffixes:
*Date,*MediaType,*LocaleCode,*Folder; plural names for arrays. - Date-times: ISO 8601 with
Z; locales:en-US. - Media types:
enumin OpenAPI spec. - Omit null properties in responses (no
anyOfwith null for optional fields).
Resource objects
Only: url, uploadId, or ACPC-related properties; optional storageType for Azure/Dropbox output URLs.
source / destination
Recommended wrapper pattern for binary inputs/outputs with peer metadata.
POST → async (Jan 2026)
Product POST endpoints should use the async calling pattern.
Severity
- error — invalid OpenAPI or lint failure
- high — style guide contract violation
- medium — doc/copy vs modular rules
- low — suggestion
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.
- 2d ago First seen · 68 lines · 0 tokens per session scan A 12a0787be9cc
api-ref-ffs-styleguide 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 597 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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.