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 efeumutaslan/SAP-SKILLS --skill sap-devops-cicdgit clone --depth 1 https://github.com/efeumutaslan/SAP-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/efeumutaslan/sap-skills/sap-devops-cicd)<a href="https://agentmods.dev/skills/efeumutaslan/sap-skills/sap-devops-cicd"><img src="https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-devops-cicd/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/efeumutaslan/sap-skills/sap-devops-cicd"><img src="https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-devops-cicd.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.00078 | $0.02895 |
| Opus 5 | $0.00039 | $0.01448 |
| Sonnet 5 | $0.00016 | $0.00579 |
| Haiku 4.5 | $0.00008 | $0.00290 |
Grade A, and why
sap-devops-cicd 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 -X POST "https://<tms-url>/v2/nodes" \ How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP DevOps & CI/CD
Related Skills
sap-testing-quality— Test automation integrated into pipelinessap-kyma-runtime— Kyma/Kubernetes deployment targetssap-s4hana-extensibility— ABAP transport and extension deployment
Quick Start
Choose your CI/CD approach:
| Scenario | Tool | Best For |
|---|---|---|
| BTP apps (CAP, UI5, MTA) | SAP CI/CD Service | Managed, no infrastructure |
| Full custom pipelines | Project "Piper" + Jenkins | Enterprise, complex workflows |
| ABAP Cloud development | ABAP Environment Pipeline | BTP ABAP Environment |
| ABAP on-premise transport | gCTS (Git-enabled CTS) | Git-based ABAP transport |
| Multi-environment promotion | Cloud Transport Management (TMS) | BTP subaccount promotion |
| Kubernetes workloads | Helm + ArgoCD / Flux | Kyma GitOps |
Minimal SAP CI/CD Service config (.pipeline/config.yml):
general:
buildTool: "mta"
productiveBranch: "main"
stages:
Build:
mtaBuildTool: "cloudMbt"
Additional Unit Tests:
npmExecuteScripts: true
npmScripts:
- "test"
Acceptance:
cloudFoundryDeploy: true
cfApiEndpoint: "https://api.cf.eu10.hana.ondemand.com"
cfOrg: "my-org"
cfSpace: "dev"
Release:
cloudFoundryDeploy: true
cfApiEndpoint: "https://api.cf.eu10.hana.ondemand.com"
cfOrg: "my-org"
cfSpace: "prod"
tmsUpload: true
Core Concepts
SAP CI/CD Service (BTP Managed)
- Managed Jenkins: No infrastructure to maintain
- Pre-configured stages: Build → Test → Deploy → Release
- Supported project types: MTA, CAP, UI5, ABAP Environment, Kyma
- Credential store: SAP Credential Store integration for secrets
- Webhook triggers: GitHub, GitLab, Bitbucket, Azure DevOps
Project "Piper" (Open Source)
- Container-based steps: Each pipeline step in a Docker container
- Library + steps: Reusable Groovy library for Jenkins
- Step catalog: 100+ steps for SAP-specific tasks
- Extensible: Custom steps in Groovy or shell scripts
- Multi-cloud: Deploy to CF, Kyma, Neo, on-premise
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 377 lines · 78 tokens per session scan A 0b7a45382746
sap-devops-cicd is a skill published in the GitHub repository efeumutaslan/SAP-SKILLS (5 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 2,895 once invoked, about $0.0004 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
repo-scaffold
Scaffold or standardize a production-ready repository structure with specs, source layout, tests, CI, agent context, config examples, release notes, and operational docs. Use when starting a new repo, turning a prototype into a maintainable project, adding missing repository foundations, or creating a repo skeleton…
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
lov-npm-publisher
An npm package publishing workflow that sets up releases through GitHub Actions using OIDC, a login-free trust method, or a local granular NPM token. It covers initial setup, publishing, audit checks, and verifying the package on the npm registry.
gh-ci-analyzer
A guide for using GitHub’s command-line tool to investigate failed GitHub Actions runs. GitHub Actions is GitHub’s system for automatically building, testing, and deploying code.
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
ci
This skill should be used when the user asks about "CI pipeline", "continuous integration", "GitHub Actions", "CI configuration", "CI jobs", "workflow", "CI caching", "CI environment", "pipeline structure", or needs guidance on setting up or configuring CI/CD pipelines.