SpaceCat API Service is an HTTP API for working with SpaceCat data, including a server-side proxy for the Semrush AIO API and a PostgreSQL-backed data service. Developers and operators use it to access and run the Edge Delivery services data system.
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/diagnose-cwvnpx skills add adobe/spacecat-api-service --skill diagnose-cwvgit clone --depth 1 https://github.com/adobe/spacecat-api-serviceWrote 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/adobe/spacecat-api-service/diagnose-cwv)<a href="https://agentmods.dev/skills/adobe/spacecat-api-service/diagnose-cwv"><img src="https://agentmods.dev/badge/skills/adobe/spacecat-api-service/diagnose-cwv.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.1 | $0.00026 | $0.00459 |
| Opus 5 | $0.00013 | $0.00230 |
| Sonnet 5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
diagnose-cwv scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
If the script is not available, replicate the checks manually using curl and jq What it actually says
Diagnose CWV
Use this skill when the user asks why CWV code patches are not being generated for a site, site ID, or opportunity.
Arguments
Accept a site URL, site ID, opportunity ID, and optional environment (dev or
prod) from the user request. If none of those identifiers is present, ask for
one before running diagnostics.
Workflow
Run the diagnostic script at
~/projects/expsuccess/spacecat/scripts/cwv/diagnose-cwv-codefix.sh with the
arguments provided by the user.
Before running, check that the required environment variables are set:
API_KEYorSESSION_TOKENmust be set in the shell; if neither is set, ask the user to run! export API_KEY=<key>;before continuing- For AWS log checks,
AWS_PROFILEshould be set
Run the script and analyze the output. The script checks these pipeline stages:
- CWV opportunity exists
- Suggestions exist with correct status
- Mystique guidance generated (data.issues[].value populated)
- Code patches generated (data.issues[].patchContent / isCodeChangeAvailable)
- Feature flags enabled (cwv-auto-suggest, cwv-auto-fix)
- S3 code repo available
- Fix entities created
- CloudWatch error logs
After the script runs, summarize the findings and identify the likely blocker. Common issues:
- No guidance: cwv-auto-suggest not enabled, or Mystique failed to process
- Guidance but no patches: cwv-auto-fix not enabled, no code repo is in S3, or the Mystique code-fix task failed
- Patches but no fix entities: Mystique or autofix-worker did not create them
- Fix entities in FAILED/ERROR: Check Mystique or autofix-worker logs for the specific error
If the script is not available, replicate the checks manually using curl and jq against the SpaceCat API.
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.
- 6d ago First seen · 52 lines · 26 tokens per session scan A b1c553b40824
diagnose-cwv is a skill published in the GitHub repository adobe/spacecat-api-service (10 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 459 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
Orchestrates Volcengine Cloud Detect (云拨测) false-alarm reduction for failing periodic-task dial points. Use for scheduled task scans, retrying failed nodes, control-testing node health, distinguishing real target outages from broken dial points, and suggesting same-type LastMile/IDC/Private replacement nodes. Runs the…