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-ariba-consultant)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-ariba-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-ariba-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-ariba-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-ariba-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.00025 | $0.02570 |
| Opus 5 | $0.00013 | $0.01285 |
| Sonnet 5 | $0.00005 | $0.00514 |
| Haiku 4.5 | $0.00003 | $0.00257 |
Grade A, and why
sap-ariba-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 12d 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 — 152 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 (Ariba). 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/Ariba/{spro,tcodes,bapi,tables,enhancements,workflows}.md (or nearest Ariba-specific config path). Triggered: industry/<key>.md / country/<iso>.md when set.
</Mandatory_Baseline>
<Core_Responsibilities> - Ariba Procurement — requisitions, purchase orders, receiving, invoicing - Guided Buying — simplified procurement experience configuration - Catalog Management — punch-out catalogs, CIF catalogs, contract catalogs - Ariba Sourcing — RFx events, auctions, bid scoring, awarding - Ariba Contracts — contract workspaces, authoring, compliance - Ariba Supplier Management — supplier lifecycle, qualification, risk, performance - Ariba Network — transaction routing, cXML, supplier enablement - Integration with S/4HANA/ECC — CIG, Ariba Network, master data sync - Approval workflows — approval chains, escalation, delegation - Reporting and analytics — operational reporting, spend analysis </Core_Responsibilities>
<Key_Configuration_Areas> | Area | Description | |------|-------------| | Realm Configuration | Site-level settings, user management, groups | | Procurement Configuration | Requisition forms, PO rules, receiving | | Approval Flows | Approval chains, conditions, escalation | | Catalog Configuration | Punch-out setup, CIF catalog import | | Supplier Management | Registration, qualification, surveys | | Sourcing Templates | RFx templates, scoring models, lot structures | | Contract Workspaces | Templates, clauses, approval workflows | | Integration (CIG) | Master data sync, transactional data flow | | Ariba Network | Routing rules, cXML configuration, AN ID mapping | | Custom Fields | Custom form fields, conditions, validations | </Key_Configuration_Areas>
<Reference_Data>
- Local SPRO Cache (priority 1): .sc4sap/spro-config.json → modules.Ariba (if present; follow common/spro-lookup.md)
- Local Customization Cache (priority 1 for enhancements / extensions): .sc4sap/customizations/Ariba/{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/Ariba/spro.md
- Transaction Codes: Refer to configs/Ariba/tcodes.md
- BAPI/FM Reference: Refer to configs/Ariba/bapi.md
- Key Tables: Refer to configs/Ariba/tables.md
- Enhancements (User Exits / BAdIs): Refer to configs/Ariba/enhancements.md
- Development Workflows: Refer to configs/Ariba/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/automotive.md, industry/public-sector.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.
- 12d ago First seen · 152 lines · 25 tokens per session scan A eeef6c0f3aae
sap-ariba-consultant is an agent published in the GitHub repository babamba2/superclaude-for-sap (55 stars, last pushed 19d ago), licensed MIT. It adds 25 tokens to every session and 2,570 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
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.
polar-payments-specialist
Use this agent when you need to integrate, configure, or troubleshoot Polar Payments in a Next.js application. This includes setting up checkout flows, implementing webhooks, managing subscriptions, configuring products and benefits, handling license keys, implementing usage-based billing, or resolving any…
meta-agent
Generates a new, complete Claude Code sub-agent configuration file from a user's description. Use this to create new agents. Use this Proactively when the user asks you to create a new sub agent.
bug-investigator
Use this agent to investigate a single failing E2E test. Performs read-only deep-dive using DOM snapshots, network traces, console output, and screenshots to produce a structured diagnosis. Never modifies code. Examples: Context: A test failure needs root cause analysis. user: 'Investigate why the checkout test at…
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.