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.
/plugin marketplace add shopwareLabs/ai-coding-toolsnpx agentmods add plugins/shopwarelabs/ai-coding-tools/ci-failure-interpretationgit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsGrade A, and why
ci-failure-interpretation 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 2d 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": "ci-failure-interpretation",
"version": "1.0.1",
"description": "Knowledge skill for interpreting CI failure logs from Shopware GitHub Actions workflows. Covers PHPUnit, PHPStan, ECS, ESLint, TypeScript, Stylelint, Prettier, Jest, Playwright, ludtwig, and Lighthouse.",
"author": { "name": "Shopware Labs" },
"license": "MIT",
"keywords": ["ci", "github-actions", "debugging", "phpunit", "phpstan", "jest", "eslint", "playwright", "lighthouse", "shopware"],
"homepage": "https://github.com/shopwareLabs/ai-coding-tools/tree/main/plugins/ci-failure-interpretation",
"repository": "https://github.com/shopwareLabs/ai-coding-tools"
}
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.
- 2d ago First seen · 11 lines scan A 1856fd47c5cc
ci-failure-interpretation is a plugin published in the GitHub repository shopwareLabs/ai-coding-tools (42 stars, last pushed yesterday), 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-08-30.
Other plugins, from other repositories
design-compare
Compare Figma designs against implementation screenshots with interactive HTML reports.
microsoft-webui
Microsoft WebUI skillset for building and debugging server-first, island-hydrated Web Components with compiled protocol-based SSR, routing workflows, and production-ready .NET host integration.
bundle-analyzer
Frontend bundle size analysis and tree-shaking optimization.
claude-ops
Claude Code operations toolkit. Twelve skills: audit-skill-visibility (audit whether each installed skill is actually VISIBLE to the model, and diagnose why most of a fleet never gets used — a skill is invisible when its description is dropped by Claude Code's skill-listing context budget, which sheds descriptions…
context-guard
Per-session context-window observability plus the first shipped consumer: a statusline wrapper tees each session's contextwindow fields to a per-session snapshot file, a zone resolver classifies usage into smart/acceptable/dumb bands (percentage bands plus window-class token bands, conservative-min combination, zones.
claude-config
Nine configuration-health skills (plus setup) for a repo's Claude Code configuration: audit (settings.json / .mcp.json / hooks / plugins / permissions drift), audit-automation-gaps (evidence-gated verdicts on automation gaps), audit-permission-grants (allow-rule / allowed-tools grants for auto-mode durability and…