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 vigneshbarani24/sap-superpowers --skill transport-releasegit clone --depth 1 https://github.com/vigneshbarani24/sap-superpowersWrote 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/vigneshbarani24/sap-superpowers/transport-release)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/transport-release"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/transport-release/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/vigneshbarani24/sap-superpowers/transport-release"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/transport-release.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.00827 |
| Opus 5 | $0.00021 | $0.00413 |
| Sonnet 5 | $0.00008 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
transport-release 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 10d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transport Release — CTS Workflow Management
This skill manages the release and promotion of transport requests through the SAP transport landscape. It enforces quality gates before each release and ensures proper CTS discipline.
Iron Laws
-
NEVER RELEASE WITHOUT PRE-RELEASE CHECKS. Every transport must pass: syntax check on all objects, ATC run clean, unit tests pass, no inactive objects, and no missing dependencies.
-
NEVER SKIP IMPORT SEQUENCE. Transports release in dependency order. If Transport B depends on Transport A, A must be imported first. Out-of-sequence imports cause dump-at-import.
-
NEVER RELEASE DIRECTLY TO PRODUCTION. All transports follow DEV → QAS → PRD. No direct modifications to production objects. No emergency transports without documented justification and post-release review.
-
ALWAYS VERIFY AFTER IMPORT. After importing into each target system, verify: no import errors, objects active, no short dumps in SM21, application works as expected.
Release Process
Step 1 — Transport Inventory
Document the transport contents:
- Transport number and description
- All objects included (type, name, action: create/modify/delete)
- Owner and development task
- Dependencies on other transports
Step 2 — Pre-Release Checks
Run all checks before releasing:
- Syntax check on every object
- ATC with project check variant
- Unit test execution for all modified classes
- Inactive object check (must be zero)
- Cross-reference check (no missing includes/dependencies)
Step 3 — Release from Development
- Release the task (developer level)
- Release the request (project lead level)
- Verify transport log is clean (return code 0 or 4, NOT 8 or 12)
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.
- 10d ago First seen · 96 lines · 42 tokens per session scan A ee3701f95e71
transport-release is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 18d ago), licensed MIT. It adds 42 tokens to every session and 827 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
sap-expert
Expert in SAP ERP systems, ABAP programming, SAP HANA, S/4HANA, Fiori applications, and SAP integration patterns including OData, RFC, and IDoc. Use when the user mentions ERP, enterprise, business apps, ABAP, HANA, or S/4HANA, or when the task involves SAP Ecosystem, ABAP Development, Integration Technologies, or…
migrate-from-openclaw
Migrate from OpenClaw to NanoClaw v2. Detects an existing OpenClaw installation, extracts identity, channel credentials, scheduled tasks, and other config, then guides interactive migration. Triggers on "migrate from openclaw", "openclaw migration", "import from openclaw".
slack-agent-flow
Let an existing Slack agent create new agents that arrive as their own Slack bots — provisioned app, operator DM, and a shared three-way room, hot-started without a host restart.
add-dial-tool
Give chosen NanoClaw agents a real phone number as a container tool — the dial CLI baked into the agent image plus OneCLI credential injection for api.getdial.ai, scoped per agent, so the agents you pick can send SMS, place AI voice calls, and receive verification codes from inside the sandbox. Independent of the Dial…
add-signal
Add Signal channel integration via signal-cli device-link. Native adapter — no Chat SDK bridge.
add-deltachat
Add DeltaChat channel integration via @deltachat/stdio-rpc-server. Native adapter — no Chat SDK bridge. Email-based messaging with end-to-end encryption.