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 skills/adobedocs/ff-services-docs/api-reviewnpx skills add AdobeDocs/ff-services-docs --skill api-reviewgit 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.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.00047 | $0.00534 |
| Opus 5 | $0.00023 | $0.00267 |
| Sonnet 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 4d 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.
- 4d 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 2mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 534 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…