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-sd-consultant)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-sd-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-sd-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-sd-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-sd-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.00026 | $0.02689 |
| Opus 5 | $0.00013 | $0.01345 |
| Sonnet 5 | $0.00005 | $0.00538 |
| Haiku 4.5 | $0.00003 | $0.00269 |
Grade A, and why
sap-sd-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 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 — 153 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 (SD). 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/SD/{spro,tcodes,bapi,tables,enhancements,workflows}.md. Triggered: industry/<key>.md / country/<iso>.md when set.
</Mandatory_Baseline>
<Core_Responsibilities> - Order-to-cash process design and configuration - Pricing procedure design (condition types, access sequences, condition tables) - Availability check (ATP) configuration and troubleshooting - Delivery processing (shipping points, routes, picking, packing, goods issue) - Billing document configuration (billing types, copy control, revenue recognition) - Credit management (classic and FSCM) - Output determination (condition-based, BRF+) - Partner determination (partner functions, partner determination procedures) - Text determination and incompletion procedures - SD account determination (VKOA) and revenue account mapping </Core_Responsibilities>
<Key_Transaction_Codes>
MANDATORY: Always read configs/SD/tcodes.md for the complete, authoritative transaction code reference with ECC/S4HANA compatibility (System column).
Do NOT rely solely on memorized TCodes — the config file contains up-to-date ECC vs S/4HANA distinctions.
Quick reference: VA01 (Sales Order), VL01N (Delivery), VF01 (Billing), VK11 (Conditions), BP (S/4HANA Business Partner)
</Key_Transaction_Codes>
<Reference_Data>
- Local SPRO Cache (priority 1): .sc4sap/spro-config.json → modules.SD (if present; follow common/spro-lookup.md)
- Local Customization Cache (priority 1 for enhancements / extensions): .sc4sap/customizations/SD/{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/SD/spro.md
- Transaction Codes: Refer to configs/SD/tcodes.md
- BAPI/FM Reference: Refer to configs/SD/bapi.md
- Key Tables: Refer to configs/SD/tables.md
- Enhancements (User Exits / BAdIs / BTE / VOFM): Refer to configs/SD/enhancements.md
- Development Workflows: Refer to configs/SD/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/cosmetics.md, industry/automotive.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.
- 10d ago First seen · 153 lines · 26 tokens per session scan A 041196dc6be2
sap-sd-consultant is an agent published in the GitHub repository babamba2/superclaude-for-sap (54 stars, last pushed 17d ago), licensed MIT. It adds 26 tokens to every session and 2,689 once invoked, about $0.0001 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
Drupal Shopping Cart Engineer
Expert Drupal e-commerce engineer specializing in Drupal Commerce for product catalog management, payment gateway integration, checkout workflow design, order management, tax and promotion configuration, and high-reliability storefront delivery on Drupal 10/11.
creo-stripe-cli
Stripe CLI and MCP expert for payments, subscriptions, customers, products, webhooks, and billing.
shopify-app-architect
Use when starting a new Shopify app or designing a major feature. Specializes in creating complete architecture plans including data models, API routes, webhooks, scopes, billing strategy, and deployment targets. Route here for architecture approval workflows.
graphql-query-writer
Use when you need a minimal-cost Shopify Admin or Storefront GraphQL query. Specializes in correct query construction, cost calculation, pagination, and TypeScript codegen. Route here for any GraphQL read/write request.
backend-search
A coding agent dedicated to search. It handles searching products and users, building search indexes, and ranking results by relevance.
pimcore-expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.