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 value-advisorygit 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/value-advisory)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/value-advisory"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/value-advisory/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/value-advisory"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/value-advisory.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.00039 | $0.03690 |
| Opus 5 | $0.00019 | $0.01845 |
| Sonnet 5 | $0.00008 | $0.00738 |
| Haiku 4.5 | $0.00004 | $0.00369 |
Grade A, and why
value-advisory 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Value Advisory
This skill enforces evidence-based business case construction so that no SAP investment claim is made without a quantification methodology, a current-state cost baseline, and explicit separation of hard savings from soft benefits — the three shortcuts that produce business cases that collapse under scrutiny.
Iron Laws
- NEVER CLAIM SAVINGS WITHOUT A QUANTIFICATION METHODOLOGY. Saying "this will reduce processing time by 40%" without documenting how that 40% was calculated is not a business case — it is a sales pitch. Every savings claim must reference its calculation method, data source, and assumptions.
- ALWAYS SEPARATE HARD SAVINGS FROM SOFT BENEFITS. Hard savings (headcount reduction, license cost elimination, error fine avoidance) are fundable. Soft benefits (improved visibility, better decisions, employee satisfaction) are not budgetable. Mixing them inflates business cases and destroys credibility when audited.
- NEVER SKIP CURRENT-STATE COST BASELINE. A business case without a current-state baseline has no reference point. "We will save X" is meaningless without "we currently spend Y." The baseline is the foundation — without it the business case is fiction.
- TCO INCLUDES TOTAL COST. Total Cost of Ownership must include: software licensing, implementation, infrastructure, integration, training, change management, ongoing support, and upgrade costs. A TCO that omits categories is not a TCO — it is a partial cost.
- BENEFIT CLAIMS REQUIRE EVIDENCE. Industry benchmarks may support a claim but cannot be the only source. Every major benefit must be validated against client-specific data: process volumes, FTE counts, error rates, cycle times measured in this organization.
Rationalization Table
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Use industry benchmark savings without client data | "Gartner says SAP reduces DSO by 15%" | Industry averages mask enormous variance. A well-run finance team may already be at benchmark. Applying average savings to a best-practice organization produces a fraudulent business case. | Iron Law 5: Every major benefit must include at least one client-specific data point (actual cycle time, actual FTE cost, actual error rate). |
| Combine hard and soft benefits in one total | "The combined value is $X million" | Finance teams immediately ask "how much is hard vs. soft?" If the answer embarrasses the business case, the case is built on soft ground. | Iron Law 2: Hard and soft benefits always reported separately, never combined into a single headline number. |
| Skip the investment cost section | "The client knows the implementation costs" | Clients systematically underestimate change management, training, and ongoing support costs. A business case that shows only benefits without full TCO is misleading and damages trust. | Iron Law 4: TCO section is mandatory. Every cost category must be addressed — even if the answer is $0. |
| Build the business case top-down from a target | "The sponsor wants to see $10M savings" | Top-down business cases reverse-engineer justifications for a predetermined conclusion. They collapse the moment a skeptic asks "where does that number come from?" | Checklist Step 2: Build bottom-up from measured baseline. Never start from a target and work backwards. |
| Use vague benefit language | "Improved efficiency and reduced manual effort" | Vague benefits cannot be tracked or audited. When value realization reviews happen 12 months post-go-live, unmeasured benefits are always deemed "not achieved." | Every benefit must have a baseline metric, target metric, measurement method, and measurement owner. |
| Ignore payback period and NPV | "The ROI is clearly positive" | ROI without time dimension is incomplete. A 200% ROI over 10 years may be inferior to a 50% ROI in 18 months depending on the organization's hurdle rate. | Checklist Step 5: Financial model must include payback period, NPV at 3 and 5 years, and IRR. |
| Claim FTE savings without workforce plan | "We will save 5 FTEs" | FTE "savings" that result in retained headcount doing lower-value work are not savings — they are redeployments. Actual savings require a workforce plan showing what happens to those FTEs. | Hard Gate: FTE savings claims must specify: reduction, redeployment to higher-value work, or natural attrition — not all three can be claimed simultaneously. |
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 · 284 lines · 39 tokens per session scan A 9e8e84a81446
value-advisory is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 16d ago), licensed MIT. It adds 39 tokens to every session and 3,690 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…
sap-rpt1
SAP-RPT-1-OSS local tabular prediction workflows for FI/CO prototype datasets. Use when preparing SAP finance CSV exports for classification or regression experiments with source-verified setup, leakage checks, and governance review.
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…
add-dashboard
Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.
customize
Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.