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/api-ref-ffs-styleguide)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/api-ref-ffs-styleguide"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/api-ref-ffs-styleguide/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/api-ref-ffs-styleguide"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/api-ref-ffs-styleguide.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.00000 | $0.00597 |
| Opus 5.5 | $0.00000 | $0.00239 |
| Sonnet 5.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 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 — 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.
- 1mo 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 3mo 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
proxy-auth-transport
Every CLI command or browser UI action that calls a crit-web API must work in both modes.
api-design-typescript
API Design for TypeScript — Express, NestJS, Fastify patterns, middleware, validation, and error handling. Extends core/rules/api-design.mdc with TypeScript-specific guidance.
api-design
API design guidelines — REST principles, GraphQL patterns, versioning, pagination, error handling, documentation, security, caching, and testing. Applied when designing or reviewing API endpoints.
node
Node.js runtime and backend best practices — configuration, process lifecycle, API robustness, async error handling, observability, and security. Applied when working on Node.js services, CLIs, or server-side code.
coderifts
CodeRifts API governance — when to preflight and how to branch.
architecture-guidelines
Guide cross-boundary, shared-module, API, data-flow, refactor, and long-lived design changes.