SAP Automation Pilot is an automation engine for SAP Business Technology Platform in which Commands define operational workflows. SAP teams use it to generate, review, deploy, run, monitor, and troubleshoot these automations. The catalogue skills provide an AI-assisted workflow for developing and operating SAP Automation Pilot Commands.
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 SAP/automation-pilot-agent-skills --skill automation-pilot-catalog-explorergit clone --depth 1 https://github.com/SAP/automation-pilot-agent-skillsWrote 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/sap/automation-pilot-agent-skills/automation-pilot-catalog-explorer)<a href="https://agentmods.dev/skills/sap/automation-pilot-agent-skills/automation-pilot-catalog-explorer"><img src="https://agentmods.dev/badge/skills/sap/automation-pilot-agent-skills/automation-pilot-catalog-explorer/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/sap/automation-pilot-agent-skills/automation-pilot-catalog-explorer"><img src="https://agentmods.dev/badge/skills/sap/automation-pilot-agent-skills/automation-pilot-catalog-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 99 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.
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.00055 | $0.00836 |
| Opus 5.5 | $0.00022 | $0.00334 |
| Sonnet 5.5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
automation-pilot-catalog-explorer 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 2mo 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 -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \ How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catalog Explorer
Discover available commands in SAP Automation Pilot dynamically via API.
Prerequisites
Environment variables must be set:
export AUTOPI_HOSTNAME="emea.autopilot.cloud.sap"
export AUTOPI_USERNAME="your-username"
export AUTOPI_PASSWORD="your-password"
API Operations
List All Catalogs
Discover what catalogs are available in the tenant.
# List all catalogs (SAP-provided + custom)
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/catalogs"
# List only SAP-provided catalogs (built-in)
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/catalogs?provided=true"
# List only custom/tenant catalogs
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/catalogs?own=true"
List Commands in a Catalog
CATALOG="applm-sapcp"
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/commands?catalog=$CATALOG"
Get Command Definition
COMMAND_ID="applm-sapcp:RestartCfApp:1"
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID"
Search Across Catalogs
Find commands matching a pattern.
# List all SAP-provided catalog IDs
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/catalogs?own=false"
# Search specific catalogs for commands matching a keyword
for catalog in applm-sapcp sm-sapcp cf-sapcp; do
echo "=== $catalog ==="
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/commands?catalog=$catalog"
done
Workflow: Complex Command Generation
When generating a command that involves multiple services:
1. User: "Create a command that restarts CF apps and checks SM bindings"
2. Discover relevant catalogs:
- Query: GET /commands?catalog=applm-sapcp
- Query: GET /commands?catalog=sm-sapcp
3. Find specific commands:
- Found: applm-sapcp:RestartCfApp:1
- Found: sm-sapcp:GetServiceBinding:1
4. Fetch definitions to understand parameters:
- GET /commands/applm-sapcp:RestartCfApp:1
- GET /commands/sm-sapcp:GetServiceBinding:1
5. Generate composite command using discovered executors
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.
- 2mo ago First seen · 108 lines · 55 tokens per session scan A e7f858a56571
automation-pilot-catalog-explorer is a skill published in the GitHub repository SAP/automation-pilot-agent-skills (13 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 836 once invoked, about $0.0002 per session on Opus 5.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
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…
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…
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…
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…