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 brainstorminggit 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/brainstorming)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/brainstorming"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/brainstorming/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/brainstorming"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/brainstorming.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.00050 | $0.03222 |
| Opus 5 | $0.00025 | $0.01611 |
| Sonnet 5 | $0.00010 | $0.00644 |
| Haiku 4.5 | $0.00005 | $0.00322 |
Grade A, and why
brainstorming 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Solution Brainstorming
This skill enforces structured, evidence-based brainstorming for SAP solutions so that no ideation session produces untethered ideas without feasibility assessment, SAP standard alignment, and clean core impact analysis.
Iron Laws
- NO IDEAS WITHOUT CONTEXT. Before generating solutions, the current state must be documented. Pain points without process context produce solutions that solve the wrong problem.
- NO SOLUTION WITHOUT SAP STANDARD CHECK. Every proposed solution must first be evaluated against SAP Best Practice content and Fit-to-Standard processes. Reinventing what SAP already provides is waste.
- NO CUSTOM WITHOUT JUSTIFICATION. Any idea requiring custom development (Z-code, BAdI, BTP extension) must include a written justification for why SAP standard or configuration cannot meet the need. Clean core is the default.
- NO IDEA WITHOUT FEASIBILITY. "Wouldn't it be great if..." is not a solution. Every idea must include: effort estimate (T-shirt size), technical feasibility, clean core impact, and dependency list.
- NO BRAINSTORM WITHOUT PRIORITIZATION. An unranked list of 20 ideas is not actionable. Every session ends with a prioritized shortlist using value vs. effort scoring.
Rationalization Table
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Jump straight to solutions | "The user described the problem clearly" | User-described problems often describe symptoms, not root causes. The real issue may be process, not system. | Checklist Step 1: Document current state BEFORE generating any solutions. |
| Suggest custom development first | "SAP standard can't do this" | 70% of "SAP can't do this" claims fail under scrutiny. New S/4HANA capabilities, Fiori apps, and BTP services often cover the need. | Iron Law 3: Check SAP standard first. Document the specific gap before proposing custom. |
| Generate a flat list of ideas | "More ideas = better brainstorm" | Flat lists overwhelm decision-makers. Without prioritization, teams pursue the exciting idea, not the valuable one. | Iron Law 5: Must produce a 2x2 prioritization matrix (value vs. effort). |
| Skip feasibility assessment | "We're just brainstorming, details come later" | Infeasible ideas that survive brainstorming consume weeks of detailed design before being killed. Kill early. | Iron Law 4: T-shirt size + feasibility flag for every idea. |
| Ignore integration implications | "That's a detail for the architects" | Solutions that don't consider integration fail during Realize. An idea that requires 5 new interfaces is not a "simple" solution. | Checklist Step 4: Every solution must list integration touchpoints. |
| Propose without considering clean core | "Clean core is aspirational, not mandatory" | SAP's lifecycle management, upgrades, and cloud transition require clean core. Extensions outside the boundary create tech debt that compounds. | Iron Law 3: Clean core impact is mandatory for every custom proposal. |
| Accept the first workable solution | "This meets the requirements" | The first workable solution is rarely the best. It anchors thinking and prevents better alternatives from emerging. | Checklist Step 3: Minimum 3 solution options per major requirement. |
| Mix strategic and tactical ideas | "All ideas are valid in brainstorming" | Mixing "move to S/4HANA Cloud" with "add a custom report field" confuses scope. Different horizons need separate treatment. | Checklist Step 2: Categorize requirements by horizon (quick win / project scope / roadmap). |
| Skip SAP Best Practice content reference | "I know what SAP standard offers" | SAP Best Practice content is updated quarterly. Agent knowledge of SAP standard may be outdated or incomplete. | Iron Law 2: Name the specific SAP Best Practice process or Fiori app that was checked. |
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 · 246 lines · 50 tokens per session scan A e832246cf022
brainstorming is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 17d ago), licensed MIT. It adds 50 tokens to every session and 3,222 once invoked, about $0.0003 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.