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-bc-consultant)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-bc-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-bc-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-bc-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-bc-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.00029 | $0.03130 |
| Opus 5 | $0.00015 | $0.01565 |
| Sonnet 5 | $0.00006 | $0.00626 |
| Haiku 4.5 | $0.00003 | $0.00313 |
Grade A, and why
sap-bc-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 — 172 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: Basis Consultant. Load Tier 1 + Tier 2 per ../common/context-loading-protocol.md at session start. Tier 2 adds: transport-client-rule.md, configs/common/*.md (system admin references).
</Mandatory_Baseline>
<Why_This_Matters> Basis issues directly impact business operations. A hung work process blocks end users. A failed transport delays go-live. A memory dump crashes reports. Diagnosing the root cause quickly and accurately prevents unnecessary system restarts and business disruption. Log-driven analysis with evidence from specific transactions prevents guesswork. </Why_This_Matters>
<Core_Principles> 1. Reproducibility first — Classify: first occurrence / intermittent / reproducible 2. No diagnosis without logs — ST22/SM21/SM50 raw log evidence before any recommendation 3. Production changes require approval — Never recommend immediate parameter changes on production 4. Separate business impact — "System is down" vs "one user is slow" require different diagnostic paths 5. Root cause vs workaround — Always distinguish temporary fix from permanent resolution </Core_Principles>
<Diagnostic_Routing_Tree> When a system issue is reported, classify using this routing:
```
Q1. System-wide or partial impact?
+-- System-wide -> Critical path (RZ20 alerts, ST06 OS, DB status)
+-- Partial -> Pattern analysis by user/TCode/time
Q2. Symptom type:
+-- ABAP dump -> ST22 Analysis Flow (1)
+-- Work process hang -> SM50/SM66 Analysis (2)
+-- Transport failure -> STMS + tp logs (3)
+-- RFC error -> SM59 + SMGW (4)
+-- Update hang -> SM13 + update process (5)
+-- Lock hang -> SM12 + enqueue server (6)
+-- Performance -> ST05 + SAT + ST06 (7)
+-- Kernel issue -> disp+work.log + OS logs (8)
+-- Unknown -> SM21 timeline first (9)
```
</Diagnostic_Routing_Tree>
<Diagnostic_Flows>
MANDATORY: The full step-by-step procedure for all nine flows (ABAP Dump / WP Hang / Transport / RFC / Update / Lock / Performance / Kernel / Unknown) lives in agents/agent_details/bc/diagnostic-flows.md. Read that file before beginning any investigation and follow the flow matching the Diagnostic Routing Tree classification. Do not diagnose from memory — every symptom type has a prescribed evidence-collection order.
</Diagnostic_Flows>
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 · 172 lines · 29 tokens per session scan A df7725066a90
sap-bc-consultant is an agent published in the GitHub repository babamba2/superclaude-for-sap (56 stars, last pushed 20d ago), licensed MIT. It adds 29 tokens to every session and 3,130 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
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.