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-copy)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/api-ref-copy"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/api-ref-copy/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-copy"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/api-ref-copy.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.00403 |
| Opus 5.5 | $0.00000 | $0.00161 |
| Sonnet 5.5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
api-ref-copy 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.
What it actually says
API reference — copy and descriptions
Response descriptions (HTTP status lines)
- Title Case, no trailing period.
- Standardize:
Success,Accepted,Bad Request,Unauthorized,Forbidden,Requested Resource Was Not Found,Too Many Requests,Internal Server Error,Input Validation Error.
All other descriptions
- Complete sentences with periods (operations, parameters, request bodies, schemas, headers).
- No trailing or leading spaces on parameter descriptions.
- Fix spelling and grammar (
eg→e.g.,etc.→etc.). - Proper acronyms: GUID, URL (not Guid, Url).
- Consistent terminology (e.g. Adobe Asset Link).
Summaries
- Sentence case; no trailing period; no
APIsuffix. - Lowercase version labels:
v1,v2(notV1). - Clear, descriptive;
operationIdin camelCase.
Public-facing text
User-visible strings must not contain internal-only information.
Scan: info, tags, operation summaries/descriptions, parameters, schemas, examples (prose), enum descriptions.
Do not allow:
- Jira or ticket keys (e.g.
FFENT-8796,PROJ-123) - Internal codenames, internal service names, corp-only wiki URLs
- Authoring TODOs tied to tickets (e.g.
TODO: fix after FFENT-…)
Allowed: Public product names, customer error codes, placeholders ({your_api_key}), standard field names (jobId).
Flag violations as high severity in eval/review output. /api-fix does not auto-fix copy — use /api-review or explicit ref-based edits.
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 · 43 lines · 0 tokens per session scan A ce6f8e7c8893
api-ref-copy 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 403 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
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).