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 agentmods add commands/secondsky/sap-skills/sac-debuggit clone --depth 1 https://github.com/secondsky/sap-skillsWrote 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/secondsky/sap-skills/sac-debug)<a href="https://agentmods.dev/commands/secondsky/sap-skills/sac-debug"><img src="https://agentmods.dev/badge/commands/secondsky/sap-skills/sac-debug.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.01402 |
| Opus 5 | $0.00008 | $0.00701 |
| Sonnet 5 | $0.00003 | $0.00280 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
sac-debug 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 today.
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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- today First seen · 219 lines · 15 tokens per session scan A fa488d401deb
sac-debug is a command published in the GitHub repository secondsky/sap-skills (432 stars, last pushed yesterday), licensed GPL-3.0. It adds 15 tokens to every session and 1,402 once invoked, about $0.0001 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 commands, from other repositories
sap-migrate
Trigger an S/4HANA migration readiness assessment — invoked when evaluating a system or landscape for conversion approach, custom code impact, simplification items, and migration risk.
sap-debug
Trigger structured root cause analysis for SAP issues — runtime errors, dump analysis, integration failures, configuration problems, or unexpected system behavior.
sap-doc
Trigger structured SAP document generation — invoked when a functional spec, technical spec, user guide, or training material needs to be produced from requirements, code, or process descriptions.
sap-estimate
Trigger structured SAP project estimation — invoked when scope needs to be broken down into effort, cost, or timeline with WBS decomposition and three-point estimates.
sap-kickoff
Trigger project kickoff for a new SAP engagement — generates a full project charter with scope, governance structure, RACI matrix, and risk register.
sap-review
Trigger a structured SAP code review — invoked when ABAP, CDS, RAP, BTP, or integration code needs to be reviewed for quality, performance, security, and clean core compliance.