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/adobe/spacecat-api-service/implement-e2e-testsnpx skills add adobe/spacecat-api-service --skill implement-e2e-testsgit clone --depth 1 https://github.com/adobe/spacecat-api-serviceWhat 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.00038 | $0.01593 |
| Opus 5 | $0.00019 | $0.00796 |
| Sonnet 5 | $0.00008 | $0.00319 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
implement-e2e-tests 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement E2E Tests
An e2e test earns its place only if it proves something no lower layer can.
test/controllers/ mocks everything and can assert any branch cheaply;
test/it/ runs the real DB/PostgREST stack with seeded, controllable personas.
Both are cheaper and faster than e2e. If a scenario is provable at either
layer, it belongs there, not here — repeating it in e2e just builds an
ice-cream cone (top-heavy on the slow, flaky layer) instead of a pyramid.
Step 1: Map the feature and its existing coverage
Identify the endpoint set from the OpenAPI paths, src/routes/index.js, and
the controller file(s) touched. Then locate what already tests them:
test/controllers/<feature>.test.js— unit, mockedtest/it/shared/tests/<feature>.js— integration, real Postgres/PostgRESTtest/e2e/<feature>.e2e.js— e2e, if this is an enhancement to an existing feature. Read it in full before writing anything — supplement it, don't fork a parallel file.
Completion: you can point at the covering file (or "none exists yet") for every candidate scenario before triaging.
Step 2: Triage — keep only what only e2e can prove
| Keep | Why unit/IT can't prove it |
|---|---|
| This route's own auth wiring: one request without a session token, asserting the real deployed middleware rejects it | Unit mocks auth; IT pre-mints valid tokens (test/it/shared/auth.js) and never calls a route unauthenticated |
Real infra wiring: entitlement/product-access from live config, facsWrapper routing, CDN/Fastly behavior, cold start |
Mocked, or stood in for by the IT harness, everywhere else |
| One assembled consumer workflow per primary intent: the call sequence a UI feature or an AI agent would actually issue, asserting the end state a user cares about | Neither layer chains calls the way a real consumer does |
| Discard | Where it already lives |
|---|---|
| Per-field/branch 400s (missing param, wrong type, bad UUID, cap/limit boundaries) | unit — cheap to enumerate exhaustively |
| Authorization matrix across roles/orgs (403 variants) | IT — has multiple seeded personas; a live dev site usually gives you only one credential |
| Version-bump / optimistic-lock / set-difference arithmetic | IT — proven against a real DB |
Anything a sinon stub or esmock'd dependency already proves |
unit |
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 · 110 lines · 38 tokens per session scan A 6e2759ef1ea0
implement-e2e-tests is a skill published in the GitHub repository adobe/spacecat-api-service (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,593 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…