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 abap-unit-testinggit 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/abap-unit-testing)<a href="https://agentmods.dev/skills/ciltress/sap-abap-mcp/abap-unit-testing"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/abap-unit-testing/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/abap-unit-testing"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/abap-unit-testing.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.03166 |
| Opus 5 | $0.00082 | $0.01583 |
| Sonnet 5 | $0.00033 | $0.00633 |
| Haiku 4.5 | $0.00016 | $0.00317 |
Grade A, and why
abap-unit-testing 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 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.
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 abap-unit-testing — 23 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ABAP Unit Testing
Guide for writing effective ABAP Unit tests including test class setup, assertions, test doubles, mocking frameworks, and test environments for CDS, SQL, and RAP.
Workflow
-
Determine the testing goal:
- Testing business logic in a class method
- Testing a CDS view entity
- Testing a RAP BO behavior implementation
- Testing database-dependent logic with SQL test doubles
- Setting up test doubles for external dependencies
-
Choose the right approach:
- Direct unit test for pure logic (no dependencies)
- Constructor/setter injection for mockable dependencies
- CDS test environment for CDS view tests
- OSQL test environment for SQL-dependent code
- RAP BO test doubles for RAP behavior tests
-
Follow the AAA pattern: Arrange → Act → Assert
-
Ensure test isolation: Tests must not depend on persistent data or external systems
Test Class Fundamentals
Test Class Definition
"! Test class for ZCL_MY_CLASS
CLASS ltc_my_class DEFINITION FINAL FOR TESTING
DURATION SHORT
RISK LEVEL HARMLESS.
PRIVATE SECTION.
DATA cut TYPE REF TO zcl_my_class. "Class Under Test
CLASS-METHODS class_setup. "Once before all tests
CLASS-METHODS class_teardown. "Once after all tests
METHODS setup. "Before each test
METHODS teardown. "After each test
METHODS test_calculate_total FOR TESTING.
METHODS test_validate_input FOR TESTING.
METHODS test_empty_input FOR TESTING RAISING cx_static_check.
ENDCLASS.
CLASS ltc_my_class IMPLEMENTATION.
METHOD class_setup.
" One-time setup for all tests in this class
ENDMETHOD.
METHOD class_teardown.
" One-time cleanup
ENDMETHOD.
METHOD setup.
" Create fresh instance before each test
cut = NEW #( ).
ENDMETHOD.
METHOD teardown.
" Cleanup after each test
ENDMETHOD.
METHOD test_calculate_total.
" Arrange
DATA(lv_quantity) = 5.
DATA(lv_price) = CONV decfloat34( '10.50' ).
" Act
DATA(lv_result) = cut->calculate_total(
iv_quantity = lv_quantity
iv_price = lv_price ).
" Assert
cl_abap_unit_assert=>assert_equals(
act = lv_result
exp = CONV decfloat34( '52.50' )
msg = 'Total should be quantity * price' ).
ENDMETHOD.
METHOD test_validate_input.
cl_abap_unit_assert=>assert_true(
act = cut->validate_input( 'VALID_INPUT' )
msg = 'Valid input should return true' ).
ENDMETHOD.
METHOD test_empty_input.
TRY.
cut->validate_input( '' ).
cl_abap_unit_assert=>fail( msg = 'Should have raised exception' ).
CATCH zcx_validation_error INTO DATA(lx_error).
cl_abap_unit_assert=>assert_bound(
act = lx_error
msg = 'Exception should be raised for empty input' ).
ENDTRY.
ENDMETHOD.
ENDCLASS.
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 · 340 lines · 165 tokens per session scan A d3aa1c6fdcd2
abap-unit-testing is a skill published in the GitHub repository Ciltress/sap-abap-mcp (3 stars, last pushed 17d ago), licensed MIT. It adds 165 tokens to every session and 3,166 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to abap-unit-testing, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.