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 basisgit 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/basis)<a href="https://agentmods.dev/skills/ciltress/sap-abap-mcp/basis"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/basis/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/basis"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/basis.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.00201 | $0.02878 |
| Opus 5 | $0.00101 | $0.01439 |
| Sonnet 5 | $0.00040 | $0.00576 |
| Haiku 4.5 | $0.00020 | $0.00288 |
Grade A, and why
basis 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Basis
Operational questions about a running system, answered from an ADT session rather than SAP GUI.
The repository skills (abap, clean-abap, rap, …) look at what is in the system. This one looks
at what the system is doing.
Who is logged on
{"tool":"listLoggedOnUsers","args":{}}
Returns a summary rather than a dump: sessionCount, userCount, then byUser (busiest first, ties
alphabetical) and byClient. A busy server has hundreds of sessions, and the summary is usually the
whole answer.
{"tool":"listLoggedOnUsers","args":{"currentUserOnly":true,"includeSessions":true}}
{"tool":"listLoggedOnUsers","args":{"user":"SOMEUSER","includeSessions":true}}
{"tool":"listLoggedOnUsers","args":{"client":"100"}}
currentUserOnly means the user this server connects as — it resolves SAP_USER itself, so do not
hard-code a name to ask "do I have a session". Every response also carries currentUser, which is
how you tell your own sessions from everyone else's.
Each session carries tid, client, user, transaction, terminal, host, time, guiVersion,
rfcType, the mode counts, and the raw logonType / logonState / logonProtocol.
Four things to know before you answer
- It is one application server, not the system.
TH_USER_LISTreports the instance your session is connected to — the equivalent ofSM04, notAL08. On a multi-instance system, "nobody is logged on" means nobody on this instance. Say so rather than implying the system is idle. logonType,logonStateandlogonProtocolare raw integers on purpose. Their data elements (UEXT_TYPE,USTATE,UPROTOCOL) have no domain, so the dictionary carries no fixed values and any label would be invented. Use the observable fields instead: atransactionand aguiVersionmean a SAP GUI dialog session; anrfcTypeofIorEmeans an RFC connection.- Most sessions are not people. Service users (
SAPJSF_*,SM*AGENT*,BGRFCSUPER,SAPSYS,RFC*,CTMAGENT,FC*) dominate the list. When asked "is anyone using the system", separate named users from technical ones instead of quoting the raw count. - A filtered result of zero is not "nobody is on". The response carries
filter.totalBeforeFilterfor exactly this reason — quote it.
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 · 215 lines · 201 tokens per session scan A 36410d527858
basis is a skill published in the GitHub repository Ciltress/sap-abap-mcp (3 stars, last pushed 17d ago), licensed MIT. It adds 201 tokens to every session and 2,878 once invoked, about $0.0010 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.