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 arc-mcp/arc-1 --skill generate-abap-unit-testgit clone --depth 1 https://github.com/arc-mcp/arc-1Wrote 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/arc-mcp/arc-1/generate-abap-unit-test)<a href="https://agentmods.dev/skills/arc-mcp/arc-1/generate-abap-unit-test"><img src="https://agentmods.dev/badge/skills/arc-mcp/arc-1/generate-abap-unit-test/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/arc-mcp/arc-1/generate-abap-unit-test"><img src="https://agentmods.dev/badge/skills/arc-mcp/arc-1/generate-abap-unit-test.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.00064 | $0.03942 |
| Opus 5 | $0.00032 | $0.01971 |
| Sonnet 5 | $0.00013 | $0.00788 |
| Haiku 4.5 | $0.00006 | $0.00394 |
Grade A, and why
generate-abap-unit-test 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 11d 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate ABAP Unit Test
Generate ABAP Unit tests for classes with dependency analysis, test doubles, and method-level surgery.
This skill replicates SAP Joule's "Unit Test Generation" capability for ABAP classes by combining ARC-1 (SAP system access) with mcp-sap-docs (documentation & best practices). Unlike the CDS unit test skill which targets CDS entities, this skill targets ABAP classes and uses interface-based test doubles instead of CDS Test Double Framework.
Smart Defaults (apply silently, do NOT ask)
| Setting | Default | Rationale |
|---|---|---|
| Test class name | ltc_<short_class_name> |
ABAP Unit tests for a global class belong in its local testclasses (CCAU) include |
| Methods to test | All public methods | User can narrow after seeing the list |
| Package | $TMP |
Fast prototyping |
| Risk level | HARMLESS |
Test doubles don't modify real data |
| Duration | SHORT |
Unit tests should be fast |
| Mock strategy | Interface-based test doubles | Cleanest pattern for dependency injection |
Input
The user provides an ABAP class to test (e.g., ZCL_TRAVEL_HANDLER).
Only the class name is required. If the user provides just a class name, apply Smart Defaults and proceed immediately.
Optionally, the user may specify:
- Test class name (default: local class
ltc_<short_class_name>inside the target class'stestclassesinclude) - Methods to test (default: all public methods)
- Package (default:
$TMP) - Transport request (only needed for non-
$TMPpackages)
Step 1: Gather Class Context
Read the class, its methods, dependencies, and any existing tests.
1a. Read the full class source
Prefer the structured format to get metadata and all includes (including existing tests) in one call:
SAPRead(type="CLAS", name="<class_name>", format="structured")
This returns JSON with metadata (description, category, package) and decomposed source (main, testclasses, definitions, implementations, macros). The testclasses field contains existing test code if any — useful for analyzing what's already covered without a separate fetch.
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.
- 11d ago First seen · 403 lines · 64 tokens per session scan A d671a99e6004
generate-abap-unit-test is a skill published in the GitHub repository arc-mcp/arc-1 (187 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 3,942 once invoked, about $0.0003 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
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.