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/vigneshbarani24/sap-superpowersWrote 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/commands/vigneshbarani24/sap-superpowers/sap-doc)<a href="https://agentmods.dev/commands/vigneshbarani24/sap-superpowers/sap-doc"><img src="https://agentmods.dev/badge/commands/vigneshbarani24/sap-superpowers/sap-doc.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.00037 | $0.00605 |
| Opus 5 | $0.00018 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
sap-doc 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sap-doc
Invokes the sap-doc-generator agent to produce structured, client-ready SAP documentation. Supports four document types, each following a standard SAP methodology template. The agent reads your input (requirements, code, process notes) and generates a fully formatted document.
Usage
/sap-doc [document type]
Document Types:
functional-spec— Functional specification (FS) from business requirements or fit-gap notestechnical-spec— Technical design document (TDS) from functional spec or codeuser-guide— End-user guide from transaction walkthrough or process descriptiontraining-material— Training module with exercises from process or system walkthrough
Examples:
/sap-doc functional-spec— then describe the requirement or paste fit-gap notes/sap-doc technical-spec— then provide the FS or point to the code file/sap-doc user-guide for VF01 billing document creation process/sap-doc training-material for MM goods receipt workflow
What Happens
- The
sap-doc-generatoragent is dispatched with the selected document type. - The agent reads the provided input — requirements, code, process description, or existing documents.
- For
functional-spec: captures business process, requirements, business rules, exception handling, and acceptance criteria. - For
technical-spec: maps functional requirements to technical design — objects, programs, interfaces, data model changes. - For
user-guide: structures step-by-step instructions with transaction paths, field-level guidance, and screenshots placeholders. - For
training-material: builds a module with learning objectives, process overview, exercises, and knowledge check questions. - The document is written to the working directory in standard SAP formatting.
Output
A formatted document file matching the selected type:
| Type | Format | Key Sections |
|---|---|---|
| functional-spec | Markdown | Business context, requirements, process flow, rules, acceptance criteria |
| technical-spec | Markdown | Architecture, objects, program design, interfaces, error handling, testing |
| user-guide | Markdown | Role overview, step-by-step instructions, field explanations, tips |
| training-material | Markdown | Objectives, process overview, guided exercises, knowledge check |
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 · 63 lines · 37 tokens per session scan A 52d9a989e841
sap-doc is a command published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 15d ago), licensed MIT. It adds 37 tokens to every session and 605 once invoked, about $0.0002 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-31.
Other commands, from other repositories
audit-xls
Audit an Excel workbook — formula errors, hardcoded cells, calculation arc cross-validation.
datasphere-mcp-tools
List all available SAP Datasphere MCP tools with descriptions and usage examples.
ui5-mcp-tools
List all available UI5 MCP server tools and their usage.
widget-lint
Analyzes SAC custom widget code for performance issues, security concerns, and best practice violations.
ui5-lint
Run UI5 linter on project with optional auto-fix and code quality analysis.
cap-deployment-checklist
Pre-deployment validation checklist for CAP applications to Cloud Foundry, Kyma, or local environments.