Borrowing it
Nothing to install: this file belongs to kts982/mcp-sap-gui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kts982/mcp-sap-gui/master/.claude/commands/sap-status.mdgit clone --depth 1 https://github.com/kts982/mcp-sap-guiWrote 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/commands/kts982/mcp-sap-gui/sap-status)<a href="https://agentmods.dev/commands/kts982/mcp-sap-gui/sap-status"><img src="https://agentmods.dev/badge/commands/kts982/mcp-sap-gui/sap-status/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/commands/kts982/mcp-sap-gui/sap-status"><img src="https://agentmods.dev/badge/commands/kts982/mcp-sap-gui/sap-status.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.00000 | $0.00221 |
| Opus 5.5 | $0.00000 | $0.00088 |
| Sonnet 5.5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
sap-status 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 2mo 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.
What it actually says
Give a quick status report on the current SAP session.
Steps:
- List all open SAP connections with
sap_list_connections - If there's an active session, connect with
sap_connect_existing - Get session info with
sap_get_session_info(system, client, user, transaction) - Get screen info with
sap_get_screen_info— checkactive_windowto see if a popup is open - If
active_windowiswnd[1]or higher, usesap_get_popup_windowfor full popup details - Take a screenshot with
sap_screenshotso the user can see the current state
Present a concise summary:
- System: system name, client, language
- User: logged-in user
- Current Transaction: t-code and screen number
- Screen: title and description
- Status Message: any current status bar message (and type: Success/Error/Warning/Info)
- Popup: whether a popup is open and what it says
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.
- 2mo ago First seen · 18 lines · 0 tokens per session scan A bfb0e27343a3
sap-status is a command published in the GitHub repository kts982/mcp-sap-gui (41 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 221 tokens. 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 commands, from other repositories
add-resolver
Add an ID resolver for a waste authority that needs internal identifiers.
update-data
Update the vendored data source and rebuild the provider registry.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.