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 yzonur/sap-adt-mcp --skill transport-release-gategit clone --depth 1 https://github.com/yzonur/sap-adt-mcpWrote 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/yzonur/sap-adt-mcp/transport-release-gate)<a href="https://agentmods.dev/skills/yzonur/sap-adt-mcp/transport-release-gate"><img src="https://agentmods.dev/badge/skills/yzonur/sap-adt-mcp/transport-release-gate/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/yzonur/sap-adt-mcp/transport-release-gate"><img src="https://agentmods.dev/badge/skills/yzonur/sap-adt-mcp/transport-release-gate.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.00131 | $0.01212 |
| Opus 5 | $0.00066 | $0.00606 |
| Sonnet 5 | $0.00026 | $0.00242 |
| Haiku 4.5 | $0.00013 | $0.00121 |
Grade A, and why
transport-release-gate 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 12d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transport Release Gate
A pre-release quality gate for SAP transport requests, built from sap-adt-mcp
tools. The philosophy: the gate decides "ready or not"; the human decides
"release". Never call adt_release_transport unless the user explicitly asks
for the release after seeing the report.
Prerequisites
- sap-adt-mcp ≥ 0.8.1 connected to the target system (
adt_pingto verify). - NetWeaver 7.50+ or S/4HANA recommended. The core flow (transport read,
syntax check, ATC worklist) works on most 7.4x+ systems, but ATC worklist
endpoints vary across releases — if
adt_run_atc_transportfails, fall back to per-objectadt_run_atc. - ATC configured on the system: a check variant must exist. The tool uses
the system default variant when none is passed; if the system has none,
ask the user for a variant name (often
DEFAULTor a Z variant). - SAP user authorizations: display for repository objects (S_DEVELOP display), transport read (S_TRANSPRT), ATC execution. Release additionally needs transport release authorization — only relevant if the user requests it.
- Read-only mode is enough for ~90% of the gate: transport read, syntax
check (
/checkruns), and ATC (/atc/) are whitelisted read-only POSTs. Unit tests (adt_run_unit_tests) require write mode — in read-only mode, skip them and note that in the report.adt_release_transportobviously requires write mode too.
Workflow
Run the steps in order; collect findings as you go instead of stopping at the first problem — the report should show everything wrong at once.
1. Resolve the transport
adt_get_transport with the TR id. Verify it exists and is modifiable
(already-released TRs can't be gated — say so and stop). Extract the object
list. If the TR is empty, report "nothing to check" and stop.
2. Cheap structural checks first
adt_list_inactive_objects— any object of this TR still inactive is an instant NO-GO (released TRs with inactive objects import broken).adt_list_locks— objects locked by other users/TRs indicate parallel work in flight; flag as a warning with the blocking TR if visible.- Optionally
adt_transport_diffagainst the target system (if a second system is configured) to preview what would change on import.
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.
- 12d ago First seen · 102 lines · 131 tokens per session scan A ccbdd540f4ab
transport-release-gate is a skill published in the GitHub repository yzonur/sap-adt-mcp (16 stars, last pushed 25d ago), licensed MIT. It adds 131 tokens to every session and 1,212 once invoked, about $0.0007 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-30.
Other skills, from other repositories
sap-abap-change-assurance
Assess an SAP transport before release by running ATC, ABAP Unit, and optional cross-system comparison, then produce JSON, SARIF, and JUnit evidence. Use when reviewing a transport, preparing a release gate, investigating a failed quality gate, or integrating SAP change checks into CI.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.