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 troubleshootinggit 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/troubleshooting)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/troubleshooting"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/troubleshooting/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/troubleshooting"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/troubleshooting.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.00033 | $0.02709 |
| Opus 5 | $0.00016 | $0.01354 |
| Sonnet 5 | $0.00007 | $0.00542 |
| Haiku 4.5 | $0.00003 | $0.00271 |
Grade A, and why
troubleshooting 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 5d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Troubleshooting
This skill enforces structured root cause analysis. It makes guessing, untested fixes, and undocumented resolutions structurally impossible.
Iron Laws
- NEVER GUESS ROOT CAUSE. "I think the problem is..." is not a root cause. Every hypothesis must be tested against evidence from SAP diagnostic tools before any fix is applied. Guessing produces wrong fixes that mask symptoms and create new problems.
- CHECK ST22 AND SM21 FIRST. Before forming any hypothesis, read the dump in ST22 and the system log in SM21. These contain the exact error, the exact stack trace, and the exact timestamp. Skipping them guarantees you are working without evidence.
- NEVER FIX WITHOUT UNDERSTANDING CAUSE. Applying a fix before the root cause is confirmed produces one of two outcomes: the fix works by coincidence (the real cause remains and will resurface), or the fix does nothing (time wasted, system still broken). Neither is acceptable.
- REPRODUCE BEFORE FIXING. If you cannot reproduce the error in a controlled way, you cannot confirm a fix has worked. A fix applied to an unreproducible error is an unverifiable fix.
- DOCUMENT ROOT CAUSE AND FIX. Every resolved incident must have a written root cause analysis. Undocumented fixes produce recurring incidents — the next consultant starts from scratch every time.
Rationalization Table
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Skip ST22 and jump to "known fixes" | "I've seen this error before, I know what it is" | The same error message can have five different root causes. Assuming you know the cause from memory is guessing with extra steps. | Iron Law 2. Open ST22. Read the full dump. The cause is in the evidence, not in memory. |
| Apply a transport or note without diagnosing | "SAP Note 1234567 fixes this class of error" | Notes fix specific causes. If your cause is different, the note changes nothing — or introduces new problems. | Iron Law 3. Confirm the root cause first. Then confirm the note addresses exactly that cause. |
| Skip reproduction because "it's intermittent" | "We can't reproduce it, so we just have to try something" | Intermittent issues have patterns — time, user, transaction, data volume. Find the pattern. Check SM21 for frequency. Use ST05 to catch the failure. | Iron Law 4. Document all known occurrence conditions. Attempt reproduction under those conditions. If truly unreproducible, escalate — do not guess. |
| Fix in production directly | "DEV doesn't have the same data, we need to fix it in PRD" | Fixing production without a tested fix path is gambling with a live system. | Reproduce in DEV or QAS. Test fix there. Transport via standard path. Emergency fixes require documented emergency change process. |
| Close the incident after the symptom disappears | "The error stopped happening, must be fixed" | Errors stop and recur. "It stopped" is not root cause. | Iron Law 5. Root cause must be identified and documented. If cause is unknown, the incident stays open. |
| Treat the first working hypothesis as confirmed cause | "That explains it, let's fix it" | The first plausible explanation is usually the simplest, not the correct one. Systems have complex interactions. | Hypothesize → Test → Confirm. A hypothesis is not confirmed until evidence from diagnostic tools supports it. |
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.
- 5d ago First seen · 182 lines · 33 tokens per session scan A 672463660b48
troubleshooting is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 16d ago), licensed MIT. It adds 33 tokens to every session and 2,709 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-09-03.
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…
sap-sac-scripting
Comprehensive SAC scripting skill for SAP Analytics Cloud Analytics Designer and Optimized Story Experience. This skill should be used when the user asks to "create SAC script", "debug Analytics Designer", "optimize SAC performance", "planning operations in SAC", "filter data in SAC", "use DataSource API", "chart…
sapui5-linter
Use this skill when working with the UI5 Linter (@ui5/linter) for static code analysis of SAPUI5/OpenUI5 applications and libraries. Covers setup, configuring linting rules, running the linter to detect deprecated APIs, global variable usage, CSP violations, and manifest issues. Supports autofix for deprecated API…
jahro-logging
Reviews and improves Debug.Log usage in Unity C# projects following structured logging principles: context tags, severity contracts, boundary-based placement, and criticality tiers. Detects common antipatterns (naked Debug.Log, logging in Update, stringly-typed errors), adds missing logs at system/state/error/external…
jahro-migration
Analyzes existing debug systems (IMGUI menus, custom loggers, cheat frameworks, performance HUDs) and generates incremental migration plans to Jahro equivalents. Use when the user wants to replace a custom debug UI, migrate from an existing console or cheat system, switch to Jahro, or has OnGUI debug code they want to…
jahro-troubleshooting
Diagnoses common Jahro issues using decision trees: commands not appearing, watcher not updating, console not opening, snapshots failing, launch button missing. Use when the user reports something not working, missing, broken, or unexpected with Jahro, or when generated Jahro code doesn't behave as expected.