Borrowing it
Nothing to install: this file belongs to AdobeDocs/ff-services-docs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AdobeDocs/ff-services-docs/main/.cursor/skills/api-review/SKILL.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/skills/adobedocs/ff-services-docs/api-review)<a href="https://agentmods.dev/skills/adobedocs/ff-services-docs/api-review"><img src="https://agentmods.dev/badge/skills/adobedocs/ff-services-docs/api-review/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/skills/adobedocs/ff-services-docs/api-review"><img src="https://agentmods.dev/badge/skills/adobedocs/ff-services-docs/api-review.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.00047 | $0.00534 |
| Opus 5.5 | $0.00019 | $0.00214 |
| Sonnet 5.5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
api-review 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 2mo 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-review — Description catalog
When to run
- User invokes
/api-review, "review API descriptions", or "catalog schema descriptions". - Do not edit the JSON unless the user later asks to
update refs N,M,…(that is not/api-fix).
Steps
-
Resolve target spec — _shared/resolve-api-spec.md. Print
**Target spec:** \path``. -
Collect text — Walk the spec in document order. Assign Ref
1,2,3, … to every user-readabledescriptionandtitle(where Redocly shows it). -
Evaluate copy — Load api-ref-copy.mdc. Fill Possible issues and Proposed content (when issues exist).
-
Emit sectioned tables — One table per section below. Location is always the last column.
Table columns
| Ref | Text (excerpt) | Possible issues | Proposed content | Location |
|---|
- Text (excerpt): ~80–120 chars; truncate with
…. - Possible issues: tags like
Missing period,Internal ID,Title Case on non-response;—if none. - Proposed content: customer-safe rewrite when issues exist;
—if OK or no safe proposal. - Location: JSON path + line number (e.g.
`components/schemas/Foo.description` · L201).
Section order
-
Info and tags
-
Operations (summary, description)
-
Parameters and request bodies
-
Responses and headers
-
Schemas (primary focus)
-
Examples (prose in example strings only)
-
Footer
- Total ref count
- Lint →
/api-fix. Copy → Proposed content orupdate refs 3, 7, 12(not/api-fix).
Batch follow-up
update refs 3, 7, 12— Apply Proposed content at Location paths; preserve meaning. Not/api-fix.
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.
- 2mo ago First seen · 49 lines · 47 tokens per session scan A 606454a3b2ce
api-review is a skill published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 534 once invoked, about $0.0002 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 skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:mapping-streaming-events
Mapping the eventable points in a Lerian Go service where lib-streaming should emit past-tense, durable, tenant-scoped business events, producing a PM-validated event catalog and instrumentation-map.json for ring:instrumenting-streaming-events. Three-pass discovery (Survey, Slice, Mark) with a scope fence and delivery…