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.
npx skills add vigneshbarani24/sap-superpowers --skill process-designgit 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/skills/vigneshbarani24/sap-superpowers/process-design)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/process-design"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/process-design.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.00049 | $0.04048 |
| Opus 5 | $0.00024 | $0.02024 |
| Sonnet 5 | $0.00010 | $0.00810 |
| Haiku 4.5 | $0.00005 | $0.00405 |
Grade A, and why
process-design 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 7d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Process Design
This skill enforces structured, evidence-based business process design for SAP implementations so that no to-be process is designed without documenting the as-is, no custom process is introduced without first validating SAP Best Practice, no process is left without an owner, and no process is complete without measurable KPIs.
Iron Laws
- NEVER DESIGN TO-BE WITHOUT DOCUMENTING AS-IS. A to-be process designed without understanding the current state is a consultant's assumption dressed as a solution. The as-is documents pain points, workarounds, data flows, and integration touchpoints that the to-be must address. Skipping it produces designs that cannot be adopted.
- REFERENCE SAP BEST PRACTICE BEFORE PROPOSING CUSTOM. Every to-be process must be compared to the relevant SAP Best Practice Scope Item before any variant or custom design is introduced. If the Best Practice meets the business need, it is the default. Custom design requires explicit justification of why Best Practice is insufficient.
- NEVER SKIP PROCESS OWNER ASSIGNMENT. A process without an accountable owner has no one to approve the design, resolve disputes in workshops, sign off on UAT, or own adoption post go-live. Every process and sub-process must have a named process owner before the design is baselined.
- DEFINE MEASURABLE KPIs FOR EVERY PROCESS. A process without KPIs cannot be improved, benchmarked, or measured for the value it delivers. Every process must have at least one leading and one lagging KPI, with a baseline value and a target value agreed with the business before Realize begins.
Rationalization Table
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Skip as-is documentation | "The client wants to move quickly — let's design the future state directly" | Without as-is, the design team misses critical integration points, data flows, exception handling paths, and user workarounds that must be addressed in the to-be. The design goes into UAT with gaps that surface as defects. | Iron Law 1: As-is documentation is not optional. If time is short, document at swim-lane level — but document it. |
| Propose custom process before checking Best Practice | "The client's process is unique — SAP standard won't work" | SAP Best Practices cover the majority of standard business scenarios. "Unique" processes are often unique habits, not unique business requirements. Best Practice adoption reduces cost, improves upgradability, and shortens delivery. | Iron Law 2: Show the Best Practice process first. Justify deviation with a named business requirement that Best Practice cannot meet. |
| Leave process owner TBD | "We'll assign owners once the design is more stable" | Design stability requires process owner input. A design without an owner cannot be reviewed, approved, or tested by the right person. The owner must co-create the design, not receive it. | Iron Law 3: Process owner is identified in Step 1 — before design begins, not after. |
| Define KPIs as generic targets | "We'll improve efficiency and reduce errors" | Generic KPIs cannot be measured, baselined, or targeted. They cannot drive remediation if adoption is poor. Without specific KPIs, the project cannot demonstrate value to the business sponsor. | Iron Law 4: Every KPI has a name, a unit of measure, a baseline value, a target value, and a measurement method. |
| Design all variants upfront | "The client has 12 variants of this process — let's document them all" | Documenting all variants before standardizing creates an unmaintainable design with 12 times the testing effort. Use variant analysis to reduce variants to the minimum necessary before designing each one. | Variant analysis step: Consolidate variants before designing. Challenge every variant with "what is the business reason this cannot follow the standard path?" |
| Skip integration touchpoints | "This is a pure finance process — no integration needed" | Pure processes are rare. Most SAP processes touch adjacent modules (FI-MM, SD-FI, PP-QM) or external systems. Missing integration touchpoints means the design is incomplete and the fit-gap analysis will be wrong. | Step 2 (as-is): Integration touchpoints are a mandatory component of the as-is documentation. |
| Treat process design as a documentation exercise | "We just need the process maps for the design spec" | Process design shapes configuration decisions, gap identification, testing scenarios, and training content. A design produced only for documentation produces designs that are disconnected from what is actually configured. | Process design drives fit-gap, configuration, and test case design. These downstream dependencies must be called out at the start of every design workshop. |
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.
- 7d ago First seen · 305 lines · 49 tokens per session scan A 894bb62c268d
process-design is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 14d ago), licensed MIT. It adds 49 tokens to every session and 4,048 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 skills, from other repositories
sap-expert
Expert in SAP ERP systems, ABAP programming, SAP HANA, S/4HANA, Fiori applications, and SAP integration patterns including OData, RFC, and IDoc. Use when the user mentions ERP, enterprise, business apps, ABAP, HANA, or S/4HANA, or when the task involves SAP Ecosystem, ABAP Development, Integration Technologies, or…
migrate-from-openclaw
Migrate from OpenClaw to NanoClaw v2. Detects an existing OpenClaw installation, extracts identity, channel credentials, scheduled tasks, and other config, then guides interactive migration. Triggers on "migrate from openclaw", "openclaw migration", "import from openclaw".
add-dial-tool
Give chosen NanoClaw agents a real phone number as a container tool — the dial CLI baked into the agent image plus OneCLI credential injection for api.getdial.ai, scoped per agent, so the agents you pick can send SMS, place AI voice calls, and receive verification codes from inside the sandbox. Independent of the Dial…
add-signal
Add Signal channel integration via signal-cli device-link. Native adapter — no Chat SDK bridge.
slack-agent-flow
Let an existing Slack agent create new agents that arrive as their own Slack bots — provisioned app, operator DM, and a shared three-way room, hot-started without a host restart.
add-deltachat
Add DeltaChat channel integration via @deltachat/stdio-rpc-server. Native adapter — no Chat SDK bridge. Email-based messaging with end-to-end encryption.