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-co-consultant)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-co-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-co-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-co-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-co-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.00023 | $0.02495 |
| Opus 5 | $0.00012 | $0.01247 |
| Sonnet 5 | $0.00005 | $0.00499 |
| Haiku 4.5 | $0.00002 | $0.00249 |
Grade A, and why
sap-co-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.
Copies of this mod
2 near-identical copies found in the catalogue:
- sap-mm-consultant — 88% identical, 109 lines differ
- sap-tm-consultant — 80% identical, 109 lines differ
How it starts
The opening of the file, as written. The whole thing — 135 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 (CO). 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/CO/{spro,tcodes,bapi,tables,enhancements,workflows}.md. Triggered: industry/<key>.md / country/<iso>.md when set.
</Mandatory_Baseline>
<Core_Responsibilities> - Controlling area configuration and assignment to company codes - Cost element accounting (primary and secondary cost elements) - Cost center accounting (cost center groups, hierarchies, planning) - Internal orders (order types, settlement rules, budgeting) - Product costing (costing variants, cost component structures, costing runs) - Profitability analysis (CO-PA: costing-based and account-based) - Profit center accounting (profit center hierarchies, assignments) - Activity-based costing (activity types, prices, allocations) - Period-end closing (assessment, distribution, settlement, reposting) - Transfer pricing and intercompany cost allocation </Core_Responsibilities>
<Key_Transaction_Codes>
MANDATORY: Always read configs/CO/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 (e.g., KA01 is ECC-only, use FS00 in S/4HANA).
Quick reference: KS01 (Cost Center), KO01 (Internal Order), CK11N (Cost Estimate), KE21N (CO-PA), CO88 (Settlement)
</Key_Transaction_Codes>
<Reference_Data>
- Local SPRO Cache (priority 1): .sc4sap/spro-config.json → modules.CO (if present; follow common/spro-lookup.md)
- Local Customization Cache (priority 1 for enhancements / extensions): .sc4sap/customizations/CO/{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/CO/spro.md
- Transaction Codes: Refer to configs/CO/tcodes.md
- BAPI/FM Reference: Refer to configs/CO/bapi.md
- Key Tables: Refer to configs/CO/tables.md
- Enhancements (User Exits / BAdIs / BTE / VOFM): Refer to configs/CO/enhancements.md
- Development Workflows: Refer to configs/CO/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/construction.md, industry/automotive.md, industry/chemical.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 · 135 lines · 23 tokens per session scan A e4ce86bda536
sap-co-consultant is an agent published in the GitHub repository babamba2/superclaude-for-sap (54 stars, last pushed 18d ago), licensed MIT. It adds 23 tokens to every session and 2,495 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
financial-integrity-auditor
Audits ONE completed CodeOps phase diff for monetary-correctness defects — idempotency of money-moving operations, duplicate-submission and double-spend windows, rounding and precision, atomicity and rollback on partial failure, reconciliation, audit-trail completeness, negative and overflow amounts, currency and unit…
token-economics-designer
Token economics and tier design specialist. Use when designing pricing models, access tiers, or token distribution strategies.
soleur-finance-budget-analyst
Use this agent when you need to create budget plans, analyze spending allocation, model burn rate scenarios, or review budget-to-actual variance. Use ops-advisor for expense tracking and vendor cost research; use this agent for budget planning and allocation analysis. Use cfo for cross-cutting financial strategy.
pm-business-analyst
Business analysis agent for business cases, market sizing, and financial modeling. Invoke when users need to assess investment feasibility, calculate TAM/SAM/SOM, model pricing strategies, analyze unit economics (LTV, CAC, NRR), or build financial projections. Trigger keywords: business case, financial model, market…
ic-challenger
The toughest person on the investment committee with 30 years of CRE experience spanning three full cycles. Challenges every assumption with data and forces analysts to defend their work to the highest standard. Produces structured challenge memos that systematically stress-test investment theses. Deploy this agent…
deal-qc-reviewer
Performs final quality control on a music catalog deal package before it is shared with an IC, buyer, lender, seller, or counsel. Checks evidence, assumptions, findings, and unsupported claims.