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 Ciltress/sap-abap-mcp --skill abapgitgit clone --depth 1 https://github.com/Ciltress/sap-abap-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/ciltress/sap-abap-mcp/abapgit)<a href="https://agentmods.dev/skills/ciltress/sap-abap-mcp/abapgit"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/abapgit/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/ciltress/sap-abap-mcp/abapgit"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/abapgit.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.00165 | $0.02153 |
| Opus 5.5 | $0.00066 | $0.00861 |
| Sonnet 5.5 | $0.00033 | $0.00431 |
| Haiku 4.5 | $0.00016 | $0.00215 |
Grade A, and why
abapgit 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 1mo 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.
This is a copy
89% identical to abapgit — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
abapGit Workflows
Guide for managing ABAP development objects in Git repositories using abapGit.
Workflow
-
Determine the user's goal:
- Setting up abapGit for the first time
- Cloning an existing repository
- Pushing ABAP code to a Git repository
- Configuring branching or transport strategies
- Setting up CI/CD pipelines for ABAP
- Troubleshooting abapGit issues
-
Identify the environment:
- On-premise SAP system with abapGit standalone
- SAP BTP ABAP Environment (abapGit integration in ADT)
- gCTS (Git-enabled Change and Transport System)
-
Guide implementation with best practices for ABAP-specific Git workflows
abapGit Overview
| Aspect | Description |
|---|---|
| What | Open-source Git client for ABAP, runs inside the SAP system |
| Serialization | Converts ABAP objects to file-based format for Git storage |
| Deserialization | Imports file-based format back into ABAP objects in the system |
| Supported Objects | Classes, interfaces, CDS, function groups, programs, tables, etc. |
| Installation | Via abapGit standalone report or Eclipse plugin |
Setup
Installing abapGit Standalone (On-Premise)
- Create report
ZABAPGIT_STANDALONEorZABAPGIT_FULL - Download latest version from https://raw.githubusercontent.com/abapGit/build/main/zabapgit_standalone.prog.abap
- Copy content into the report and activate
- Run the report via
SE38or transactionZABAPGIT
abapGit in ADT (BTP ABAP Environment)
- In ADT: Window → Show View → Other → abapGit Repositories
- Link repository using HTTPS URL
- Requires communication arrangement for Git service
SSL Certificates
- Download GitHub/GitLab root certificates
- Import via
STRUST(transaction) → SSL Client (Anonymous) or (Standard) - Required for HTTPS connections to Git providers
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.
- 1mo ago First seen · 267 lines · 165 tokens per session scan A 32e4228653f7
abapgit is a skill published in the GitHub repository Ciltress/sap-abap-mcp (3 stars, last pushed 6d ago), licensed MIT. It adds 165 tokens to every session and 2,153 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to abapgit, differing in 26 lines, and is treated as a copy.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.