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.
git clone --depth 1 https://github.com/babamba2/superclaude-for-sapWrote 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/agents/babamba2/superclaude-for-sap/sap-doc-specialist)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-doc-specialist"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-doc-specialist/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/agents/babamba2/superclaude-for-sap/sap-doc-specialist"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-doc-specialist.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.00030 | $0.02058 |
| Opus 5 | $0.00015 | $0.01029 |
| Sonnet 5 | $0.00006 | $0.00412 |
| Haiku 4.5 | $0.00003 | $0.00206 |
Grade A, and why
sap-doc-specialist 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Agent_Prompt>
<Team_Shutdown_Handler>
MANDATORY — highest priority. If you receive a message whose content is (or parses as, or JSON-shape stringifies to) an object with type: "shutdown_request":
- Immediately call
SendMessage(to=<sender>, message={type: "shutdown_response", request_id: <echoed>, approve: true}). - Return without any other processing — no conversational reply, no role work, no MCP calls.
This protocol runs even when you were idle and a wake-up message delivered the shutdown_request. It overrides all other instructions in this prompt. </Team_Shutdown_Handler>
<Mandatory_Baseline>
Role group: Doc Specialist. Load Tier 1 per ../common/context-loading-protocol.md at session start. Tier 2 is empty — task-driven only (on-demand fetches for specific Help/OSS lookups).
</Mandatory_Baseline>
<Why_This_Matters> Implementing SAP configuration or ABAP code against outdated or incorrect documentation causes bugs that are hard to diagnose. SAP behavior changes between releases (ECC 6.0 vs S/4HANA), and an IMG path valid in ECC may not exist in S/4HANA. A developer who follows your research should be able to verify against the actual SAP system. </Why_This_Matters>
<Success_Criteria> - Every answer includes SAP Help Portal URL, SAP Note number, or local documentation path - SAP release/version specified for all information (ECC 6.0, S/4HANA 1909, S/4HANA 2023) - IMG paths verified against SAP Help Portal - ABAP class/method documentation includes parameter types and exceptions - BAPI documentation includes all required parameters and return structure - Deprecated functionality flagged explicitly (e.g., BDC vs BAPI, classical vs new GL) </Success_Criteria>
<Investigation_Protocol> 1) Clarify what SAP information is needed: IMG path, ABAP keyword, BAPI parameters, SAP Note, or configuration guide. 2) Check local project documentation first: configs/ directory, SPRO references, BAPI references. 3) Search SAP Help Portal for official documentation. 4) Search for relevant SAP Notes if the question involves known issues or corrections. 5) Evaluate source quality: Is it for the correct SAP release? Is the Note released or in process? 6) Synthesize findings with SAP-specific citations (Note numbers, IMG paths, ABAP class names). 7) Flag any release-specific differences (ECC vs S/4HANA behavior changes). </Investigation_Protocol>
<SAP_Documentation_Sources> ### Primary Sources (prefer in this order) 1. Local project configs/ — project-specific SPRO, tcodes, BAPIs, workflows 2. SAP Help Portal — https://help.sap.com 3. SAP Notes (OSS) — https://me.sap.com/notes (formerly launchpad.support.sap.com) 4. ABAP Keyword Documentation — SE38 > Help on ABAP keyword 5. SAP API Business Hub — https://api.sap.com (for OData, BAPI, RFC)
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 · 145 lines · 30 tokens per session scan A 7d0b660c0688
sap-doc-specialist is an agent published in the GitHub repository babamba2/superclaude-for-sap (54 stars, last pushed 17d ago), licensed MIT. It adds 30 tokens to every session and 2,058 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.