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 skills add adobe/spacecat-api-service --skill plg-suggestion-grantsgit 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/plg-suggestion-grants)<a href="https://agentmods.dev/skills/adobe/spacecat-api-service/plg-suggestion-grants"><img src="https://agentmods.dev/badge/skills/adobe/spacecat-api-service/plg-suggestion-grants/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adobe/spacecat-api-service/plg-suggestion-grants"><img src="https://agentmods.dev/badge/skills/adobe/spacecat-api-service/plg-suggestion-grants.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 86 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 174 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00131 | $0.04873 |
| Opus 5 | $0.00066 | $0.02436 |
| Sonnet 5 | $0.00026 | $0.00975 |
| Haiku 4.5 | $0.00013 | $0.00487 |
Grade A, and why
plg-suggestion-grants 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 9d 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.
curl -s "$POSTGREST/tokens?select=*&site_id=eq.<siteId>" -H "Authorization: Bearer $TOKEN" How it starts
The opening of the file, as written. The whole thing — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PLG Suggestion Grants (check / revoke / regrant)
Drives @adobe/spacecat-shared-utils's PLG token-quota system for
suggestions, implemented in
src/support/grant-suggestions-handler.js
and exposed indirectly through the opportunities/suggestions controllers.
Each PLG site gets a small monthly quota ("token") of suggestions it's
allowed to see per opportunity type — this skill lets you inspect that state
and force a refresh (revoke anything stale, backfill with the current best).
This mutates a real site's PLG token allocation in whichever environment
you point it at. There is no dedicated "revoke" or "regrant" endpoint you
call with a body — the revoke+regrant cycle is a side effect of GET /sites/:siteId/opportunities/:opportunityId, gated behind the site's
entitlement tier. Treat every trigger call here as a real action against
that environment's data — same spirit as the plg-onboard skill's safety
gate — and be especially careful on prod, where it's customer-facing.
Target environment
Ask which environment (dev, stage, or prod) before doing anything,
unless the user already said. Default to prod only after confirming — a
real PLG customer's token allocation lives there, so don't assume.
| Env | App API base | PostgREST base | Auth |
|---|---|---|---|
prod |
https://spacecat.experiencecloud.live/api/v1 |
https://d1xldhzwm6wv00.cloudfront.net |
mysticat auth token / mysticat login (defaults to prod) |
stage |
https://spacecat.experiencecloud.live/api/stage |
(none — see caveat below) | mysticat auth token --env stage / mysticat login --env stage |
dev |
https://spacecat.experiencecloud.live/api/ci |
https://dql63ofcyt4dr.cloudfront.net |
mysticat auth token --env dev / mysticat login --env dev |
Caveat — no separate stage PostgREST instance. The app API has all three
environments, but the PostgREST reporting service (used for every read-only
inspection step below) only has dev and prod deployments — confirmed
against the query-sites/query-opportunities skills' own endpoint tables,
neither of which lists a stage URL. If the target is stage, you can still
trigger the app-API refresh call against /api/stage, but you cannot verify
grant/token state via PostgREST for a stage-only site — the dev PostgREST
instance won't have that site's rows either. Say this limitation out loud
rather than silently querying the wrong environment's data.
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.
- 9d ago First seen · 332 lines · 131 tokens per session scan A 4d71b14eb21c
plg-suggestion-grants is a skill published in the GitHub repository adobe/spacecat-api-service (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 131 tokens to every session and 4,873 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…