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-explore.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-explore)<a href="https://agentmods.dev/commands/kts982/mcp-sap-gui/sap-explore"><img src="https://agentmods.dev/badge/commands/kts982/mcp-sap-gui/sap-explore.svg" alt="Measured on agentmods" 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.00378 |
| Opus 5 | $0.00000 | $0.00189 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
sap-explore 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 7d 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
Explore the current SAP screen and report what you find.
Steps:
- Connect to the existing SAP session using
sap_connect_existing - Get session info with
sap_get_session_infoto know where we are - Get screen info with
sap_get_screen_info— checkactive_windowin the response:- If
wnd[0]: normal screen, continue with step 4 - If
wnd[1]or higher: a popup is open — usesap_get_popup_windowfor full details and report it first
- If
- Discover all screen elements with
sap_get_screen_elementson the active window's user area - Get available toolbar buttons with
sap_get_toolbar_buttons - If the screen contains a table or grid (look for element types containing
GuiGridVieworGuiTableControl):- Read the table data with
sap_read_table(limit to 20 rows) - Note the
table_typein the response - If ALV: also get the ALV toolbar buttons with
sap_get_alv_toolbar - If TableControl: note the scroll position and total rows
- Read the table data with
- If the screen contains a tree control, read it with
sap_read_tree(limit to 50 nodes)
Present a clear summary:
- Transaction: current transaction code and screen number
- Screen Title: what this screen is for
- Status: any status bar messages
- Input Fields: list changeable fields with their current values and labels
- Tables/Grids: column names, row counts, and first few rows of data
- Available Actions: toolbar buttons, function key shortcuts
- Suggested Next Steps: what the user might want to do on this screen
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.
- 7d ago First seen · 26 lines · 0 tokens per session scan A 0617c3ebad7c
sap-explore is a command published in the GitHub repository kts982/mcp-sap-gui (29 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 378 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
python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.
seo-report
Generates a complete SEO report in markdown — combines technical audit, content and schema in one document with an overall score and prioritized action plan. TRIGGER when the user enters /seo-report or asks for a full SEO report, SEO summary or SEO audit report.
seo-content
Analyzes content quality — length, readability, thin content, internal duplicate content and topic expansion opportunities. TRIGGER when the user enters /seo-content or asks to analyze content quality, thin content, readability or topic coverage.
seo-audit
Full technical SEO audit of a site. Reviews meta tags, headings, images without alt, broken links, sitemap, robots.txt, canonical tags and URL structure. Generates a report prioritized by impact. TRIGGER when the user enters /seo-audit or asks for a complete SEO audit.
seo-compare
Compares the SEO of two pages or your page against a competitor. Shows differences in meta tags, structure, content, schema and speed side by side. TRIGGER when the user enters /seo-compare or asks to compare pages, analyze a competitor or see SEO differences between two URLs.
seo-meta
Reviews and generates optimized meta titles and descriptions for all pages. Checks length, keywords, uniqueness and potential CTR. TRIGGER when the user enters /seo-meta or asks to review, improve or generate meta tags, title tags or meta descriptions.