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/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/data-intelligence-pipeline-check)<a href="https://agentmods.dev/commands/secondsky/sap-skills/data-intelligence-pipeline-check"><img src="https://agentmods.dev/badge/commands/secondsky/sap-skills/data-intelligence-pipeline-check.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.1 | $0.00025 | $0.00304 |
| Opus 5 | $0.00013 | $0.00152 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
data-intelligence-pipeline-check 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 4d 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.
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.
- 4d ago First seen · 39 lines · 25 tokens per session scan A aca6eb42c701
data-intelligence-pipeline-check is a command published in the GitHub repository secondsky/sap-skills (436 stars, last pushed 4d ago), licensed GPL-3.0. It adds 25 tokens to every session and 304 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-fi-closing
A step-by-step checklist for closing SAP Financial Accounting records at the end of a month or year. It covers accounting periods, unpaid invoices, assets, foreign currencies, journal entries, and financial-statement checks.
sap-ibp-forecast-debug
A diagnostic checklist for SAP Integrated Business Planning, a cloud system used to plan demand, supply, and inventory. It checks forecast settings, historical data, product and location mappings, and job logs.
agent-system-prompt
Write a system prompt for an AI agent that defines its role, tools, boundaries, and output clearly enough to act reliably.
prompt-eval-debug
Debug any prompt with a tiny eval suite (control, edge, boundary), failure diagnosis, and smallest next change, no blind rewrite.
content-pipeline
Run the full multi-agent content production pipeline.
checklist
Generate a custom checklist for the current feature based on user requirements.