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-cloud-migrationgit 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-cloud-migration)<a href="https://agentmods.dev/skills/ciltress/sap-abap-mcp/abap-cloud-migration"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/abap-cloud-migration/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-cloud-migration"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/abap-cloud-migration.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.00170 | $0.02726 |
| Opus 5 | $0.00085 | $0.01363 |
| Sonnet 5 | $0.00034 | $0.00545 |
| Haiku 4.5 | $0.00017 | $0.00273 |
Grade A, and why
abap-cloud-migration 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 10d 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
100% identical to abap-cloud-migration — 0 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ABAP Cloud Migration Patterns
Guide for systematically migrating classic ABAP custom code to ABAP Cloud (Tier 1) compliance.
Workflow
- Assess current state: Run ATC Cloud Readiness checks on existing code
- Categorize findings: Group by finding type (unreleased API, language construct, etc.)
- Plan migration: Prioritize by impact and determine replacement strategy
- Implement replacements: Apply released API replacements or create wrappers
- Validate: Re-run ATC checks and test functionality
Migration Assessment
Running ATC Cloud Readiness Checks
- In ADT: Right-click package → Run As → ABAP Test Cockpit
- Use check variant
ABAP_CLOUD_READINESSor a custom variant with cloud-relevant checks - Review findings in the ATC Results view
Key ATC Check Messages
| Message ID | Description | Action |
|---|---|---|
NROB |
Use of unreleased number range API | Use CL_NUMBERRANGE_RUNTIME |
BAPI |
Direct BAPI call | Use released RAP API or wrapper |
DYNP |
Dynpro/screen usage | Replace with Fiori/UI5 |
FUGR |
Unreleased function module call | Find released replacement or wrap |
CLAS |
Unreleased class usage | Find released replacement or wrap |
TABL |
Direct DB table access (not released) | Use released CDS view entity |
LANG |
Incompatible language construct | Refactor to use modern ABAP |
Common API Replacements
Database Access
| Classic Pattern | ABAP Cloud Replacement |
|---|---|
SELECT FROM mara |
SELECT FROM i_product |
SELECT FROM bkpf / bseg |
SELECT FROM i_journalentry |
SELECT FROM vbak / vbap |
SELECT FROM i_salesorder |
SELECT FROM ekko / ekpo |
SELECT FROM i_purchaseorder |
SELECT FROM kna1 |
SELECT FROM i_customer |
SELECT FROM lfa1 |
SELECT FROM i_supplier |
SELECT FROM t001 |
SELECT FROM i_companycode |
| Direct table access | Use I_* released CDS views |
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.
- 10d ago First seen · 289 lines · 170 tokens per session scan A 27121089ad3b
abap-cloud-migration is a skill published in the GitHub repository Ciltress/sap-abap-mcp (3 stars, last pushed 18d ago), licensed MIT. It adds 170 tokens to every session and 2,726 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to abap-cloud-migration, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…