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/ui5-linter-check)<a href="https://agentmods.dev/commands/secondsky/sap-skills/ui5-linter-check"><img src="https://agentmods.dev/badge/commands/secondsky/sap-skills/ui5-linter-check/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/secondsky/sap-skills/ui5-linter-check"><img src="https://agentmods.dev/badge/commands/secondsky/sap-skills/ui5-linter-check.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.00028 | $0.00280 |
| Opus 5 | $0.00014 | $0.00140 |
| Sonnet 5 | $0.00006 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
ui5-linter-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 5d 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.
- 5d ago First seen · 39 lines · 28 tokens per session scan A ffb2b144cfd5
ui5-linter-check is a command published in the GitHub repository secondsky/sap-skills (438 stars, last pushed 5d ago), licensed GPL-3.0. It adds 28 tokens to every session and 280 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-korean-tax-invoice-debug
A Korean-language troubleshooting command for electronic tax invoices, which are digital business invoices reported through Korea's tax systems, across SAP and several invoice providers.
sap-performance-check
A checklist for diagnosing SAP system performance across hardware, databases, SAP work processes, application code, and networks. SAP is business software used to run operations such as finance, purchasing, and production.
sap-session-start
A command guide for starting an evidence-based SAP troubleshooting session. It records an initial symptom, creates a session ID, and prepares folders for evidence, hypotheses, requests, and conclusions.
sap-transport-debug
A command guide for diagnosing failed SAP STMS transports. STMS is SAP's system for moving development changes between systems; the guide covers transport status, logs, return codes, and common dependency problems.
sap-payment-run-debug
A guided troubleshooting process for failed F110 payment runs in SAP, where F110 creates scheduled payments to vendors.
sap-migo-debug
A diagnostic command for MIGO, SAP’s screen for posting material receipts and other inventory movements. It checks possible causes in a set order, including stock, movement types, accounting, periods, and material costs.