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 project-kickoffgit 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/project-kickoff)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/project-kickoff"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/project-kickoff/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/project-kickoff"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/project-kickoff.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.00040 | $0.02915 |
| Opus 5 | $0.00020 | $0.01458 |
| Sonnet 5 | $0.00008 | $0.00583 |
| Haiku 4.5 | $0.00004 | $0.00292 |
Grade A, and why
project-kickoff 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Project Kickoff
This skill enforces structured SAP project initiation so that no project starts without a charter, governance model, stakeholder register, and risk register — the four artifacts that prevent the "we assumed someone else was handling that" failures that kill SAP programs.
Iron Laws
- NO PROJECT WITHOUT A CHARTER. A verbal agreement is not a project. A charter with scope, governance, milestones, and sign-off authority is a project. Everything else is a favor.
- NO SCOPE WITHOUT BOUNDARIES. In-scope means nothing without explicit out-of-scope. Every charter must list both. Ambiguous scope is the #1 cause of SAP project overruns.
- NO GOVERNANCE WITHOUT ESCALATION PATHS. A steering committee that meets monthly is not governance. Defined escalation paths with SLAs and named decision-makers is governance.
- NO RACI WITHOUT VALIDATION. A RACI created by one person is a wish list. A RACI validated by every Accountable party is a commitment.
- NO KICKOFF WITHOUT RISK REGISTER. Projects that start without identified risks are not optimistic — they are negligent. Minimum 5 risks with quantified impact.
- ACTIVATE PHASES ARE NON-NEGOTIABLE. Every SAP project maps to SAP Activate phases (Discover, Prepare, Explore, Realize, Deploy, Run). Custom phase names create confusion with SAP support and quality gates.
Rationalization Table
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Skip stakeholder analysis | "The project sponsor told us who matters" | Sponsors have blind spots. Missed stakeholders surface at UAT with blocking objections. | Checklist Step 1: Minimum 4 stakeholder categories (executive, process owner, end user, IT). |
| Define scope as a bullet list | "The SOW already has the scope" | Bullet lists lack precision. "Implement FI" could mean 2 company codes or 50. | Iron Law 2: Scope must include entity counts, process boundaries, and explicit exclusions. |
| Skip the communication plan | "We'll figure out communication as we go" | Ad-hoc communication means the steering committee learns about risks from rumors. | Checklist Step 5: Communication plan with audience, frequency, channel, and owner for each stakeholder group. |
| Create a RACI in isolation | "I know the org chart" | Org charts show reporting lines, not project accountability. The FI lead may not know they own chart of accounts migration. | Iron Law 4: Every A (Accountable) party must confirm in writing. |
| Use generic risk categories | "Risks are risks — resource, budget, timeline" | Generic risks generate generic mitigations. "Data migration complexity" with a specific legacy system named drives action. | Checklist Step 6: Each risk must name a specific SAP module, system, or workstream. |
| Assume SAP Activate is understood | "Everyone knows Activate" | Teams confuse Activate with Waterfall, ASAP, or their own hybrid. Phase gates get skipped. | Iron Law 6: Charter must map deliverables to Activate phases explicitly. |
| Skip the out-of-scope section | "We listed what's in scope, isn't that enough?" | What you don't list, the client assumes is included. Especially integrations, reports, data migration. | Iron Law 2: Out-of-scope section is mandatory and must be at least half as long as in-scope. |
| Copy a charter template without customizing | "This template worked for the last project" | Every SAP landscape is different. A retail S/4HANA project charter does not fit a pharma brownfield migration. | Verification: Charter must reference this client's specific systems, modules, and org structure. |
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 · 243 lines · 40 tokens per session scan A 9b62413fc9af
project-kickoff is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 17d ago), licensed MIT. It adds 40 tokens to every session and 2,915 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
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
slack-construct-agents
Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
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…
roadmap-interview
Run a short product-discovery interview with a user of Kochab to surface what they actually need, then turn it into structured roadmap input. Use when someone says "interview me about features," "run the roadmap interview," "I have feedback on the tool," "what should this tool do next," or when a maintainer wants to…
eso-guild-social-manager
Creates, updates, and uses ESO GUILD.md files for guild discovery and social planning. Use when finding, evaluating, joining, tracking, or interacting with ESO guilds.