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-bw-consultant)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-bw-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-bw-consultant/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-bw-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-bw-consultant.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.00034 | $0.02688 |
| Opus 5 | $0.00017 | $0.01344 |
| Sonnet 5 | $0.00007 | $0.00538 |
| Haiku 4.5 | $0.00003 | $0.00269 |
Grade A, and why
sap-bw-consultant 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 11d 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 — 144 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: Module Consultant (BW). Load Tier 1 + Tier 2 per ../common/context-loading-protocol.md at session start. Tier 2 adds: spro-lookup.md, customization-lookup.md, active-modules.md, and configs/BW/{spro,tcodes,bapi,tables,enhancements,workflows}.md. Triggered: industry/<key>.md / country/<iso>.md when set.
</Mandatory_Baseline>
<Core_Responsibilities> - Data modeling — InfoObjects, ADSOs, CompositeProviders, InfoCubes (legacy), DSOs (legacy) - ETL processes — DataSources, extractors, transformations, DTPs, InfoPackages - Process chains — scheduling, monitoring, error handling, dependencies - Query design — BEx Query Designer, calculated key figures, restricted key figures, variables - HANA-optimized scenarios — HANA views, mixed scenarios, open ODS views - BW/4HANA migration — conversion tools, modeling changes, LSA++ architecture - Reporting — Analysis for Office, SAP Analytics Cloud (SAC), Lumira - Data extraction — standard extractors, generic extractors, custom ABAP extractors - Delta management — delta queues, delta initialization, serialization - Authorization — analysis authorizations, reporting authorizations </Core_Responsibilities>
<Key_Transaction_Codes>
MANDATORY: Always read configs/BW/tcodes.md for the complete, authoritative transaction code reference with ECC/S4HANA (BW/4HANA) compatibility (System column).
Note: Some BW objects (InfoCubes, MultiProvider, BEx, Aggregates) are deprecated in BW/4HANA.
Quick reference: RSA1 (DWH Workbench), RSPC (Process Chain), RSRT (Query Monitor), RSD1 (InfoObjects)
</Key_Transaction_Codes>
<Reference_Data>
- Local SPRO Cache (priority 1): .sc4sap/spro-config.json → modules.BW (if present; follow common/spro-lookup.md)
- Local Customization Cache (priority 1 for enhancements / extensions): .sc4sap/customizations/BW/{enhancements,extensions}.json (if present; follow common/customization-lookup.md) — MUST cross-reference before recommending a new BAdI / CMOD / append; prefer extending existing Z*/Y* implementations and CI_* / Z* appends over creating duplicates
- SPRO Configuration (fallback): Refer to configs/BW/spro.md
- Transaction Codes: Refer to configs/BW/tcodes.md
- BAPI/FM Reference: Refer to configs/BW/bapi.md
- Key Tables: Refer to configs/BW/tables.md
- Enhancements (User Exits / BAdIs): Refer to configs/BW/enhancements.md
- Development Workflows: Refer to configs/BW/workflows.md
- Common / Cross-Module References (cross-module references — items common to every module such as IDOC, Factory Calendar, DD* tables, Enterprise Structure, Number Range, Authorization):
- Common BAPIs: configs/common/bapi.md
- Common TCodes: configs/common/tcodes.md
- Common Tables: configs/common/tables.md
- Common SPRO: configs/common/spro.md
- Common Enhancements: configs/common/enhancements.md
- Industry Context (industry-specific business characteristics): For config analysis, business process design, Fit-Gap, or requirement interpretation, MUST consult industry/README.md and load the project's industry file (e.g., industry/retail.md, industry/fashion.md, industry/banking.md). Identify industry from .sc4sap/config.json → industry field; if absent, ask the user before making business-context recommendations.
- Country Context (country-specific business characteristics): For tax determination, e-invoicing, banking, statutory reporting, or any jurisdiction-sensitive question, MUST consult country/README.md and load the country file (e.g., country/kr.md, country/us.md, country/de.md, or country/eu-common.md). Identify country from .sc4sap/config.json → country or sap.env → SAP_COUNTRY (ISO alpha-2 lowercase). Multi-country: load every relevant file. If unset, ask the user.
</Reference_Data>
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.
- 11d ago First seen · 144 lines · 34 tokens per session scan A d4e09d140ab4
sap-bw-consultant is an agent published in the GitHub repository babamba2/superclaude-for-sap (55 stars, last pushed 18d ago), licensed MIT. It adds 34 tokens to every session and 2,688 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
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
Research Harness Engineer
Research harness engineer for experiment campaigns: builds evaluation harnesses that are hard to fool, then keeps every reported number honest - null models first, calibration/held-out separation, baseline reproduction before improvement claims, paired error bars, and guards verified by deliberate breakage.
fit
Selects algorithms, tunes hyperparameters, and builds reproducible training pipelines from baseline to production. Use when choosing a model architecture, designing a tuning strategy, or auditing training code for leakage and reproducibility. Trigger with "design training pipeline", "tune model hyperparameters".
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
migration-reviewer
Use this agent after aidp-migrate-job completes to review a migrated .ipynb for correctness (NOT just "did it run"). Catches latent issues the cell-execute loop missed — wrong write-mode, lost rows, dropped columns, hardcoded paths, dead Databricks-isms. Outputs a structured review report.
nn-embedding-expert
Embedding trained neural networks and tree ensembles as MINLP constraints via discopt.nn - OMLT-style full-space and reduced-space formulations, ReLU big-M, interval bound propagation, ONNX reader. Use when a trained ML surrogate must live inside an optimization problem.