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 likweitan/abap-skills --skill badi-enhancementgit clone --depth 1 https://github.com/likweitan/abap-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/likweitan/abap-skills/badi-enhancement)<a href="https://agentmods.dev/skills/likweitan/abap-skills/badi-enhancement"><img src="https://agentmods.dev/badge/skills/likweitan/abap-skills/badi-enhancement/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/likweitan/abap-skills/badi-enhancement"><img src="https://agentmods.dev/badge/skills/likweitan/abap-skills/badi-enhancement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00232 | $0.04407 |
| Opus 5.5 | $0.00093 | $0.01763 |
| Sonnet 5.5 | $0.00046 | $0.00881 |
| Haiku 4.5 | $0.00023 | $0.00441 |
Grade A, and why
badi-enhancement 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- badi-enhancement — 100% identical, 188 lines differ
How it starts
The opening of the file, as written. The whole thing — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BAdI & Enhancement Framework
Guide for using BAdIs (Business Add-Ins) and the ABAP enhancement framework to extend SAP standard functionality, with clean core level classification for each technique.
BAdIs are the only recommended enhancement technology under the clean core level concept. The ATC check
SYCM_ALLOWED_ENH_TECHNOLOGYreportsENHOenhancements built on any other technology as a priority 1 (Level D) finding.
Workflow
-
Determine the user's goal:
- Finding an existing BAdI to implement
- Creating a custom BAdI definition
- Implementing a BAdI
- Replacing a modification or implicit enhancement with a BAdI
- Understanding classic vs. new enhancement framework
- Using key user extensibility
- Classifying an enhancement's clean core level
-
Identify the framework:
- New BAdI framework (preferred, ABAP Cloud compatible)
- Classic BAdI framework (legacy,
SE18/SE19) - Enhancement spots and implementations
- Key user extensibility (no-code)
-
Classify the clean core level using the table below
-
Guide implementation toward the highest applicable level
Clean Core Level by Enhancement Technique
| Technique | Level | Guidance |
|---|---|---|
| Key user extensibility | A | Start here for tightly coupled extensions — custom fields, custom logic, custom CDS views |
| Released BAdI | A | Preferred code-based extension point |
| Released extension include | A | Preferred technique for custom fields on DB tables and CDS views |
| Released extension point / RAP BO | A | Use for extending RAP-based SAP Fiori apps |
| CDS extends / metadata extensions | A/B | Extend SAP CDS views rather than modifying them |
| Non-released BAdI | B | Good choice for classic extensions even when not released for cloud development. Monitor for release |
User exits (VOFM, SAPMV45A) |
B | Predefined SAP coding parts are stable and typically survive upgrades. Technically a modification |
| Customer exits (SMOD/CMOD) | B | Predecessor of BAdIs. Use only where no BAdI exists — likely to be replaced in future releases |
| Non-released extension include | B | Acceptable; monitor when a released extension include becomes available |
| DDIC appends (CI / EEW includes) | B | Append fields via customer includes or extension includes |
| Domain value appends, search help appends/exits | B | Acceptable classic extension techniques |
| OData service redefinition | B | Redefine rather than modify |
| Classic append on DB table | C | Monitor when an extension include becomes available and adapt accordingly |
| Explicit enhancement spots | B/D | Exceptional cases only, to include a custom BAdI. Do not place extension code directly in the spot |
| Implicit enhancement spots | D | Similar to a modification — do not use |
| Source code plug-ins | D | ATC priority 1 finding — delete and use a BAdI |
| SAP-internal-flagged BAdI | D | Exceptional cases only |
| Modifications | D | Avoid completely. If unavoidable, use the modification assistant and govern via ATC |
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.
- 1mo ago Changed · +140 lines · +48 tokens per session 99b3d27c289a
- 1mo ago First seen · 292 lines · 184 tokens per session scan A f7337ac9a702
badi-enhancement is a skill published in the GitHub repository likweitan/abap-skills (72 stars, last pushed 11d ago), licensed MIT. It adds 232 tokens to every session and 4,407 once invoked, about $0.0009 per session on Opus 5.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-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…
sap-integration-wiki
Guide for integrating external systems (Java, Python, .NET, Node.js, low-code) with SAP (ECC 6.0, S/4HANA On-Premise/Cloud): OData V2/V4, RFC/JCo, SOAP-over-HTTP RFC without JCo, IDoc/PI-PO, BAPI, RAP, BTP Integration Suite/iFlow, Event Mesh, Cloud Connector, Communication Arrangements, FI-AA, AR/AP, Central Finance…
sap-abap
Comprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing, dynamic programming, RTTI/RTTC, field…
sap-btp-developer-guide
Develops business applications on SAP Business Technology Platform (BTP) using CAP (Node.js/Java) or ABAP Cloud. Use when: building cloud applications on SAP BTP, deploying to Cloud Foundry or Kyma runtimes, integrating with SAP HANA Cloud, implementing SAP Fiori UIs, connecting to remote SAP systems, building…
sap-btp-integration-suite
Enterprise integration solutions using SAP Integration Suite on BTP. Covers Cloud Integration (iFlows), API Management, Event Mesh, Edge Integration Cell, Integration Advisor, Trading Partner Management, and Migration Assessment. Use for building integration flows, managing API proxies, event-driven architectures…
sap-cap-capire
SAP Cloud Application Programming Model (CAP) development skill using Capire documentation. Use when: building CAP applications, defining CDS models, implementing services, working with SAP HANA/SQLite/PostgreSQL databases, deploying to SAP BTP Cloud Foundry or Kyma, implementing Fiori UIs, handling authorization…