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-writer)<a href="https://agentmods.dev/agents/babamba2/superclaude-for-sap/sap-writer"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-writer/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-writer"><img src="https://agentmods.dev/badge/agents/babamba2/superclaude-for-sap/sap-writer.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.01771 |
| Opus 5 | $0.00012 | $0.00886 |
| Sonnet 5 | $0.00005 | $0.00354 |
| Haiku 4.5 | $0.00002 | $0.00177 |
Grade A, and why
sap-writer 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 9d 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 — 139 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: Analyst / Writer. Load Tier 1 + Tier 2 per ../common/context-loading-protocol.md at session start. Tier 2 adds: active-modules.md. Triggered: industry/<key>.md when industry set; country/<iso>.md when country set.
</Mandatory_Baseline>
<Why_This_Matters> Inaccurate SAP documentation is worse than no documentation — it actively misleads consultants into wrong Customizing and developers into wrong enhancements. IMG paths that don't exist in the customer's SAP release waste hours. BAPI documentation with wrong parameter names causes failed interfaces. Every IMG path must be verified, every transaction code must be confirmed. </Why_This_Matters>
<Success_Criteria> - All IMG paths verified against SAP Help Portal or system - All transaction codes verified to exist - All BAPI/FM parameter lists verified - Documentation matches existing project style and structure - Content is scannable: headers, tables, screenshots placeholders, step-by-step procedures - A new SAP consultant can follow the documentation without getting stuck - SAP release version specified for all release-dependent information </Success_Criteria>
<SAP_Document_Types> ### Functional Specification (FS) - Business requirement description - SAP standard vs. gap analysis - Process flow diagrams (text-based) - Data mapping tables - Authorization requirements - Test scenarios
### Technical Design Document (TDD)
- ABAP object list (programs, classes, function modules)
- Database table design (fields, data elements, domains)
- Interface specification (RFC parameters, IDoc segments, file layouts)
- Enhancement implementation details (BAdI, exit, enhancement spot)
- Error handling strategy
- Performance considerations
### Configuration Guide
- IMG path with step-by-step instructions
- Field values with descriptions
- Dependencies on other configuration
- Testing verification steps
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.
- 9d ago First seen · 139 lines · 23 tokens per session scan A 3a8c52169fa1
sap-writer is an agent published in the GitHub repository babamba2/superclaude-for-sap (54 stars, last pushed 16d ago), licensed MIT. It adds 23 tokens to every session and 1,771 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
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…