ecommerce-cms-skills

Install

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.

Security

Grade A, and why

ecommerce-cms-skills 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 3d 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.

.claude-plugin/plugin.json · 10 lines

What it actually says

{
  "name": "ecommerce-cms-skills",
  "description": "Best practices and development guidelines for Intershop, Shopware 6, and Storyblok",
  "version": "1.0.0",
  "author": {
    "name": "Benedikt Grimm",
    "url": "https://github.com/bartundmett"
  }
}

Contents

What it installs

The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 249 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Files

What ships with it

1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

Related

Other plugins, from other repositories