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/BoxLogoDev/sapstackWrote 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/plugins/boxlogodev/sapstack/sap-wm)<a href="https://agentmods.dev/plugins/boxlogodev/sapstack/sap-wm"><img src="https://agentmods.dev/badge/plugins/boxlogodev/sapstack/sap-wm/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/plugins/boxlogodev/sapstack/sap-wm"><img src="https://agentmods.dev/badge/plugins/boxlogodev/sapstack/sap-wm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sap-wm 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 2mo 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.
What it actually says
{
"name": "sap-wm",
"version": "1.0.0",
"description": "Warehouse structure, storage type/bin, transfer order, putaway/picking strategies, physical inventory in WM. Legacy ECC module — deprecated in S/4HANA (use EWM).",
"depends_on": [],
"reuses_agents": []
}What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 202 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2mo ago First seen · 7 lines scan A e8624340590d
sap-wm is a plugin published in the GitHub repository BoxLogoDev/sapstack (20 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-04.
sap-wm compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sap-wmBoxLogoDev/sapstack | Plugin | 20 | 1mo ago | MIT | A | — | Claude Code |
| moysklad-mcp-ruilyautov/moysklad-mcp-ru | Plugin | 3 | 5d ago | MIT | A | — | Claude Code |
| moysklad-mcp-ruilyautov/moysklad-mcp-ru | Plugin | 3 | 5d ago | MIT | A | — | Gemini CLI |
| b2c-cliSalesforceCommerceCloud/b2c-developer-tooling | Plugin | 58 | today | Apache-2.0 | A | — | Claude Code |
| maqami-travelnegm17111995/mcp-server | Plugin | 2 | 21d ago | MIT | A | — | Gemini CLI |
| mcp-pinterest-brand-presence-mappermambalabsdev/mcp-pinterest-brand-presence-mapper | Plugin | 0 | 2d ago | MIT | A | — | Cursor |
| tray-apitray-tecnologia/tray-api-ai-plugin | Plugin | 15 | 2mo ago | MIT | A | — | Claude Code |