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 change-managementgit 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/change-management)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/change-management"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/change-management/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/vigneshbarani24/sap-superpowers/change-management"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/change-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.04062 |
| Opus 5 | $0.00021 | $0.02031 |
| Sonnet 5 | $0.00008 | $0.00812 |
| Haiku 4.5 | $0.00004 | $0.00406 |
Grade A, and why
change-management 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 10d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Change Management
This skill enforces structured, evidence-based change management for SAP implementations so that no stakeholder group goes unanalyzed, no communication is broadcast without targeting, no training is generic, and adoption is measured before go-live is declared successful.
Iron Laws
- NEVER SKIP STAKEHOLDER IMPACT ANALYSIS. Deploying SAP without a stakeholder impact analysis is deploying into the unknown. You do not know who is most affected, who will resist, or who needs to be onside first. Every role that touches the new system must be analyzed before communication or training begins.
- NEVER ASSUME ONE CHANNEL REACHES ALL. An email to all staff is not a communication strategy. Different stakeholder groups have different access, literacy, and trust in different channels. Segment your audiences and match channel to group.
- ALWAYS CREATE ROLE-BASED TRAINING. Generic "how to use SAP" training fails because it does not connect to the user's actual daily tasks. Every training audience must be defined by role, and every training module must be tied to the transactions and processes that role performs.
- DEFINE ADOPTION METRICS BEFORE GO-LIVE. If you have not defined what adoption looks like, you cannot measure it, and you cannot declare go-live successful. Metrics must be agreed with the business before cutover — not retrospectively applied to explain poor outcomes.
Rationalization Table
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Skip formal stakeholder impact analysis | "We know who the users are — let's go straight to communication" | Knowing who the users are is not the same as knowing who is most impacted, what changes they face, and how ready they are. Unanalyzed stakeholders become resistant users. | Iron Law 1: Complete the stakeholder impact matrix before any communication or training is designed. |
| Send a single all-staff communication | "Everyone needs to know about SAP — one message covers it" | Different roles face different changes. A warehouse operator and a finance controller have entirely different concerns. One message addresses neither properly and builds distrust in both. | Iron Law 2: Segment audiences. Map message to role, concern, and channel. |
| Use a single generic training course | "SAP training is SAP training — we'll cover all modules in one session" | Generic training produces low retention and high support ticket volume post go-live. Users learn SAP in the abstract but cannot perform their own jobs in the new system. | Iron Law 3: Training is designed per role. Each role gets a module tied to its transactions and process steps. |
| Define adoption metrics after go-live | "We'll measure adoption once the system is live and we can see actual usage" | Post go-live metric definition means you have no baseline, no agreed target, and no ability to trigger remediation. By the time low adoption is visible, the window for intervention has closed. | Iron Law 4: Adoption metrics are agreed and baselined before cutover rehearsal. |
| Treat resistance as an IT problem | "Users will adapt once the system is live" | Resistance is a change problem, not a system problem. Unmanaged resistance causes workarounds, parallel processing, shadow systems, and eventually failed adoption. | Resistance management step: Identify resistance sources early. Engage resistors directly — do not route around them. |
| Compress change management into the Deploy phase | "We'll do training and communication in the last month before go-live" | Change management that starts in Deploy is too late. Awareness must be built in Prepare, understanding in Explore, acceptance in Realize, readiness in Deploy. Compressing it creates surface-level readiness that collapses under go-live pressure. | Phase alignment: Change management activities must be planned against SAP Activate phases from Prepare onward. |
| Treat change management as a soft track | "Change management is important but the real work is configuration" | Failed SAP implementations are more commonly the result of adoption failure than technical failure. Change management is a risk mitigation activity, not a soft-skills add-on. | Frame change management outputs as risk controls — stakeholder impact = risk identification, training = risk mitigation, adoption metrics = risk acceptance criteria. |
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.
- 10d ago First seen · 319 lines · 42 tokens per session scan A 4ea27853239b
change-management is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 18d ago), licensed MIT. It adds 42 tokens to every session and 4,062 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…
cae-tutor
A comprehensive CAE (Cambridge C1 Advanced) exam preparation tutor for self-studying students. Activate this skill whenever a student mentions the CAE, C1 Advanced, Cambridge Advanced English, or any of its component papers (Reading & Use of English, Writing, Listening, Speaking). Also trigger for requests like…
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-codex
Use Codex (OpenAI's codex app-server) as a full agent provider — planning, tool orchestration, MCP tools, server-side history, session resume — alongside or instead of Claude. ChatGPT subscription or OpenAI API key, vault-only via OneCLI. Per-group via ncl groups config update --provider codex. Distinct from using…
baoyu-comic
A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.
add-dashboard
Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.