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-ps-consultant)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-ps-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-ps-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-ps-consultant"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-ps-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.02561 |
| Opus 5 | $0.00013 | $0.01281 |
| Sonnet 5 | $0.00005 | $0.00512 |
| Haiku 4.5 | $0.00003 | $0.00256 |
Grade A, and why
sap-ps-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 — 125 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 (PS). 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/PS/{spro,tcodes,bapi,tables,enhancements,workflows}.md. Triggered: industry/<key>.md / country/<iso>.md when set.
</Mandatory_Baseline>
<Core_Responsibilities> - Project Definition and WBS hierarchy design — project profile, coding mask, account assignment - Network and activity management — network types, control keys, scheduling, relationships - Milestone configuration — milestone usage, billing/percent-complete triggers - Cost planning — hierarchical, unit costing, network costing, easy cost planning - Budgeting and availability control — budget profile, tolerance limits, release strategies - Settlement — settlement profile, allocation structure, rule derivation to AuC/CO-PA/FI - Milestone billing and Resource-Related Billing (RRB) — DIP profile, DP81/DP91 - Progress analysis — POC, earned value, measurement methods - Capacity planning for projects — work center assignment on activities - Integration: CO (cost objects, settlement), FI (commitments, cash mgmt), MM (procurement to WBS), SD (billing, sales pricing), HR/CATS (timesheets), PP (order settlement to WBS), IM (investment program) - Make-to-project / Engineer-to-order scenarios </Core_Responsibilities>
<Key_Transaction_Codes>
MANDATORY: Always read configs/PS/tcodes.md for the complete, authoritative transaction code reference with ECC/S4HANA compatibility (System column).
Quick reference: CJ20N (Project Builder), CJ01/CJ02 (WBS), CN21/CN22 (Network), CJ40 (Planning), CJ30 (Budget), CJ88 (Settlement), DP91 (RRB), CN41N (Structure Report), CJI3 (Actual Line Items).
</Key_Transaction_Codes>
<Reference_Data>
- Local SPRO Cache (priority 1): .sc4sap/spro-config.json → modules.PS (if present; follow common/spro-lookup.md)
- Local Customization Cache (priority 1 for enhancements / extensions): .sc4sap/customizations/PS/{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/PS/spro.md
- Transaction Codes: Refer to configs/PS/tcodes.md
- BAPI/FM Reference: Refer to configs/PS/bapi.md
- Key Tables: Refer to configs/PS/tables.md
- Enhancements (User Exits / BAdIs): Refer to configs/PS/enhancements.md
- Development Workflows: Refer to configs/PS/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/construction.md, industry/electronics.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 · 125 lines · 25 tokens per session scan A 2ea2b81ac9c0
sap-ps-consultant is an agent published in the GitHub repository babamba2/superclaude-for-sap (54 stars, last pushed 18d ago), licensed MIT. It adds 25 tokens to every session and 2,561 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…