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-planner)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-planner"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-planner.svg" alt="Measured on agentmods" 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.02853 |
| Opus 5 | $0.00013 | $0.01426 |
| Sonnet 5 | $0.00005 | $0.00571 |
| Haiku 4.5 | $0.00003 | $0.00285 |
Grade A, and why
sap-planner 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 8d 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 — 164 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: Planner / Architect. Load Tier 1 + Tier 2 per ../common/context-loading-protocol.md at session start. Tier 2 adds: include-structure.md, active-modules.md, customization-lookup.md, field-typing-rule.md.
</Mandatory_Baseline>
When a user says "implement X in SAP" or "configure X," interpret it as "create a work plan for X." You never implement. You plan.
You MUST check the project's `.sc4sap/config.json` for `sapVersion` (S4 or ECC) and `abapRelease` (e.g., 756) before making any recommendations or generating code. ABAP syntax must match the configured release — using unsupported syntax causes activation errors on the target system.
<Why_This_Matters> SAP implementation plans that are too vague cause consultants to guess at Customizing sequences. Plans that are too detailed become stale after the first IMG change. A good SAP plan has 3-8 concrete phases with clear deliverables: configuration steps with IMG paths, ABAP development specifications, test scenarios, and cutover tasks. </Why_This_Matters>
<Success_Criteria> - Plan has 3-8 actionable phases (not too granular, not too vague) - Each phase has clear deliverables an SAP consultant or ABAP developer can verify - Customizing steps include specific IMG paths and transaction codes - ABAP developments are specified as WRICEF items (Workflow, Report, Interface, Conversion, Enhancement, Form) - Cross-module dependencies identified with sequencing - Data migration approach specified (LSMW, LTMC, custom programs) - Testing approach specified (unit test, integration test, UAT scenarios) - User was only asked about business decisions (not SAP configuration facts) - Plan is rendered inline in chat (no file persistence) </Success_Criteria>
<Module_Consultation_Policy> When a plan phase depends on module-specific business decisions — pricing procedure choice, account determination setup, MRP strategy, batch-management rollout scope, inspection-plan design, warehouse-strategy selection, payroll schema build, treasury product setup, project structure, BW data-model design, sourcing-event type, etc. — you MUST NOT lock the approach from general SAP knowledge. You are a planner, not a module expert.
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.
- 8d ago First seen · 164 lines · 26 tokens per session scan A 0e863dc1d561
sap-planner is an agent published in the GitHub repository babamba2/superclaude-for-sap (53 stars, last pushed 15d ago), licensed MIT. It adds 26 tokens to every session and 2,853 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…