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/release-outage-responsenpx skills add adobe/spacecat-api-service --skill release-outage-responsegit 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/release-outage-response)<a href="https://agentmods.dev/skills/adobe/spacecat-api-service/release-outage-response"><img src="https://agentmods.dev/badge/skills/adobe/spacecat-api-service/release-outage-response.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.00165 | $0.01774 |
| Opus 5 | $0.00082 | $0.00887 |
| Sonnet 5 | $0.00033 | $0.00355 |
| Haiku 4.5 | $0.00016 | $0.00177 |
Grade A, and why
release-outage-response 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 5d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release-Caused Outage Response
LLM-led companion to docs/runbooks/release-caused-outage.md. The runbook holds
the exact commands and the worked example; this skill enforces the sequence,
the diagnosis discipline, and the one hard safety gate.
Before starting, read docs/runbooks/release-caused-outage.md — work from its
commands rather than reconstructing them. This skill tells you what to do and in
what order; the runbook tells you how.
Operating rules
- Diagnose before reverting. Do not propose a revert until evidence supports it. Hold at least two hypotheses until one is confirmed (see Phase 2–3).
- One hard gate: never run the revert or the push to prod
mainwithout explicit human confirmation (Phase 4). This is the only irreversible, shared-state action in the flow — treat it as such. - Verify locally first. A revert is cheap, but a wrong revert wastes the one
cheap mitigation you have. Prove the suspect build is broken before you touch
main(Phase 3). - Narrate for an operator under pressure. State what you found and what you're about to do in plain, skimmable terms — someone is watching this incident.
Workflow
Phase 1 — Confirm and frame the outage
- Pull live errors (
npm run logs/ Splunkindex=dx_aem_engineering sourcetype=dx_aem_sites_spacecat_backend_prod service=api-service level=error | sort -_time). Run it via themcp__splunk__search_splunkMCP tool, or open the UI: https://splunk.or1.adobe.net/en-US/app/search/search?q=search%20index%3Ddx_aem_engineering%20sourcetype%3Ddx_aem_sites_spacecat_backend_prod%20service%3Dapi-service%20level%3Derror%20%7C%20sort%20-_time&earliest=-1h&latest=now - Establish: is it broad (all/most requests) or scoped to one endpoint/tenant? If scoped, stop — this skill is for release-wide outages; diagnose that endpoint instead.
- Optionally confirm black-box with the auth-free health check (runbook Step 1) — a
load-time failure fails even
/_status_check/healthcheck.json. - Capture the exact error and the first-occurrence timestamp.
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.
- 5d ago First seen · 134 lines · 165 tokens per session scan A 1d3b45bc4300
release-outage-response is a skill published in the GitHub repository adobe/spacecat-api-service (10 stars, last pushed today), licensed Apache-2.0. It adds 165 tokens to every session and 1,774 once invoked, about $0.0008 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…