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 babamba2/superclaude-for-sap --skill package-to-processgit 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/skills/babamba2/superclaude-for-sap/package-to-process)<a href="https://agentmods.dev/skills/babamba2/superclaude-for-sap/package-to-process"><img src="https://agentmods.dev/badge/skills/babamba2/superclaude-for-sap/package-to-process/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/skills/babamba2/superclaude-for-sap/package-to-process"><img src="https://agentmods.dev/badge/skills/babamba2/superclaude-for-sap/package-to-process.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Excessive Agency · line 87 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00079 | $0.02607 |
| Opus 5 | $0.00039 | $0.01303 |
| Sonnet 5 | $0.00016 | $0.00521 |
| Haiku 4.5 | $0.00008 | $0.00261 |
Grade A, and why
sc4sap:package-to-process 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SC4SAP Package → End-to-End Business Process
Reads ONE CBO package via MCP, classifies its programs/FMs into business document flows (PR → PO → GR → IR, SO → DN → Billing, etc.), and renders a Markdown narrative for functional consultants. Unlike analyze-cbo-obj (static inventory of reusable elements) or program-to-spec (single-object spec), this skill produces a process-level story spanning multiple programs with Mermaid diagrams + per-step tables.
<Response_Prefix>
Every response triggered by this skill MUST begin with [Model: <main-model> · Dispatched: <sub-summary>] per ../../common/model-routing-rule.md § Response Prefix Convention.
</Response_Prefix>
<Phase_Banner>
Multi-phase skill. Before each Agent(...) dispatch, emit ▶ phase=<id> (<label>) · agent=<name> · model=<Opus 4.7|Sonnet 4.6|Haiku 4.5> per ../../common/model-routing-rule.md § Phase Banner Convention.
</Phase_Banner>
<Progress_Bar> Every Step entry MUST print a one-line progress indicator in this exact form (no ANSI colors, 20-char bar, right-aligned percentage):
Step X/7 · <label> [██████░░░░░░░░░░░░░░] 29%
- Bar width = 20 chars, filled =
█, empty =░ - Percentage =
floor(step_id × 100 / 7)at entry (Step 0 = 0%, Done = 100%) - Authoritative mapping table:
workflow.md§ Progress Reporting
The bar is the only progress feedback for the user during long Steps 4–6 (multi-minute analyst dispatches), so it MUST be printed before each Step starts. </Progress_Bar>
<Use_When>
- User says: "package to process", "패키지 프로세스 분석", "E2E 비즈니스 흐름 문서화", "패키지 분석해서 process flow", "reverse-engineer process from package"
- AMS / handover preparation: need a process-level map of an unfamiliar Z-package
- Fit/Gap review: need to see how the customer's CBO implements a business process before judging gaps
- Onboarding new consultants/developers onto an existing module </Use_When>
<Do_Not_Use_When>
- User wants only the reusable-object catalog →
/sc4sap:analyze-cbo-obj - User wants a single program spec →
/sc4sap:program-to-spec - User wants to compare 2–5 programs side-by-side →
/sc4sap:compare-programs - User wants code quality review →
/sc4sap:analyze-code - Package has zero PROG/FUGR (process narrative is meaningless without entry points) </Do_Not_Use_When>
<Session_Trust_Bootstrap> MANDATORY — runs as Step 0 before any MCP call or user interaction.
Invoke /sc4sap:trust-session with parent_skill=sc4sap:package-to-process to pre-grant MCP tool + file-op permissions (eliminates per-tool prompts during package walk + where-used graph + analyst/writer dispatches).
- If
.sc4sap/session-trust.logalready has a line within the last 24h, skip silently. - Otherwise run it and surface the one-line confirmation.
Full spec: see ../trust-session/SKILL.md.
</Session_Trust_Bootstrap>
<Companion_Files> MANDATORY: Read the companion files below before executing. Each covers a self-contained section:
| Companion | Scope |
|---|---|
workflow.md |
7-step execution flow + Progress Reporting (bar template + step→% table) |
grouping-heuristics.md |
Auto-grouping algorithm: shared-table clustering + module-specific document-flow dictionary (MM/SD/PP/PM/QM/FI/CO) |
document-template.md |
Master .md skeleton: frontmatter + auto-TOC + per-process section + Mermaid (flowchart + sequenceDiagram) + tables |
dispatch-stocker.md |
Step 2 — sap-stocker auto-chain (conditional, inventory missing) |
dispatch-analyst.md |
Steps 4 & 5 — sap-analyst grouping + per-process narrative |
dispatch-writer.md |
Step 6 — sap-writer master .md render |
bpml-render.md |
Step 6b — BPML deliverable: spec-JSON contract + build-bpml.mjs CLI (xlsx/md/both) + language rules |
| </Companion_Files> |
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 140 lines · 79 tokens per session scan A b4af80aa480d
sc4sap:package-to-process is a skill published in the GitHub repository babamba2/superclaude-for-sap (54 stars, last pushed 16d ago), licensed MIT. It adds 79 tokens to every session and 2,607 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…