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.
git 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/commands/vigneshbarani24/sap-superpowers/sap-kickoff)<a href="https://agentmods.dev/commands/vigneshbarani24/sap-superpowers/sap-kickoff"><img src="https://agentmods.dev/badge/commands/vigneshbarani24/sap-superpowers/sap-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/commands/vigneshbarani24/sap-superpowers/sap-kickoff"><img src="https://agentmods.dev/badge/commands/vigneshbarani24/sap-superpowers/sap-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.00033 | $0.00623 |
| Opus 5 | $0.00016 | $0.00311 |
| Sonnet 5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
sap-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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sap-kickoff
Invokes the project-kickoff skill to structure and document the start of an SAP project or phase. Enforces that scope, governance, roles, and risks are defined before any delivery work begins. Produces a client-ready project charter.
Usage
/sap-kickoff [project name]
Arguments:
[project name]— The name or brief description of the project. Additional context (client, modules, deployment model) will be gathered through the skill's structured intake process.
Examples:
/sap-kickoff Acme Group S/4HANA Greenfield — Phase 1 Discovery/sap-kickoff RetailCo RISE with SAP migration — FI CO MM SD/sap-kickoff BTP Integration Layer for HealthCo — Phase 2 Realize
What Happens
- The
project-kickoffskill activates and runs a structured intake — project type, client details, scope, team size, deployment model, timeline. - The skill enforces governance definition before proceeding — steering committee, decision authority, escalation paths must be named.
- RACI matrix is built for all key roles: workstream leads, client counterparts, SI team, hyperscaler contacts.
- Risks are identified and rated using a probability/impact matrix — not listed generically.
- Success criteria and measurable outcomes are captured explicitly.
- The skill chains to
estimationskill if effort has not yet been confirmed. - Output is a structured project charter file ready for client review.
Output
A Project Charter document containing:
| Section | Content |
|---|---|
| Project Overview | Objectives, scope statement, out-of-scope |
| Delivery Approach | SAP Activate phases, milestones, timeline |
| Governance | Steering committee, decision-making authority, meeting cadence |
| RACI Matrix | All roles mapped to responsibilities |
| Team Structure | Org chart with workstream leads and client contacts |
| Risk Register | Top 10 risks with probability, impact, and mitigation |
| Success Criteria | Measurable outcomes tied to business value |
| Assumptions & Constraints | Named explicitly — nothing implied |
| Sign-off Block | Approval section for client and SI leads |
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 · 62 lines · 33 tokens per session scan A c4c2be8ec391
sap-kickoff is a command published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 17d ago), licensed MIT. It adds 33 tokens to every session and 623 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 commands, from other repositories
sac-planning-checklist
Generate a comprehensive checklist for SAC planning implementation projects.
runs
List live and persisted CCAM-launched Claude Code and Codex runs.
project-health
Audit and manage project configuration — permissions, context, docs.
datasphere-mcp-tools
List all available SAP Datasphere MCP tools with descriptions and usage examples.
ui5-mcp-tools
List all available UI5 MCP server tools and their usage.
widget-lint
Analyzes SAC custom widget code for performance issues, security concerns, and best practice violations.