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-fixnpx skills add AdobeDocs/ff-services-docs --skill api-fixgit 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.00057 | $0.00518 |
| Opus 5 | $0.00028 | $0.00259 |
| Sonnet 5 | $0.00011 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
api-fix 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.
What it actually says
/api-fix — Fix lint and structure
Scope
Apply mechanical fixes from two sources:
- Redocly lint — issues reported by
npm run lint:openapi -- <path> - Structure — inconsistencies with api-ref-structure.mdc
Do not apply FFS style guide changes, copy edits, description punctuation, internal IDs, examples polish, or api-ref-schema / api-ref-copy findings unless Redocly flags them.
Steps
-
Resolve target spec — _shared/resolve-api-spec.md.
-
Run lint — Record all errors/warnings.
-
Structure pass — Load api-ref-structure.mdc. Fix:
- Top-level section order:
openapi→info→servers→security→tags→paths→components - Missing
info.license(Adobe Creative API License boilerplate) - Validity issues lint may not cover: broken
$ref, duplicate schema names (when clearly wrong) - Reorder keys only; do not rewrite endpoint or schema semantics
- Top-level section order:
-
Lint pass — Fix each Redocly finding with minimal change. Cite rule/message.
-
Re-run lint until zero errors (warnings per reference.md).
-
Re-check structure — Confirm section order and license after lint edits.
-
Report — Separate what was fixed under Lint vs Structure. If clean but style/copy issues remain, say: Run
/api-evalfor style guide and documentation findings.
Out of scope
- FFS async shapes,
error_codealignment, tags, summaries, public-facing text anyOf/type-array cleanup unless Redocly flags it- Large refactors of file organization beyond section reorder and license
Reference
See reference.md for Redocly rules and structure checklist.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 46 lines · 57 tokens per session scan A 58ed3852f85d
api-fix is a skill published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 518 once invoked, about $0.0003 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.