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/contributor-writinggit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsGrade A, and why
contributor-writing 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": "contributor-writing",
"version": "1.6.6",
"description": "Writing skills for Shopware core contributors: Architecture Decision Records, PR descriptions (trunk and feature-branch formats), commit messages, and RELEASE_INFO/UPGRADE entries. Analyzes branch diffs, classifies changes, and writes content calibrated to change magnitude.",
"author": { "name": "Shopware Labs" },
"license": "MIT",
"keywords": ["adr", "architecture", "decision-records", "release-info", "upgrade", "changelog", "release-notes", "documentation", "pull-request", "pr-description", "feature-branch", "commit-message", "conventional-commits", "shopware"],
"homepage": "https://github.com/shopwareLabs/ai-coding-tools/tree/main/plugins/contributor-writing",
"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 a1d2e71aa45d
contributor-writing 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
ship
Commit, push, create PR with confirmation at every step, then optional cleanup of branches whose remotes are gone. Blocks secrets and force-push.
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.
context-budget
Measure a Claude Code session's fixed startup context payload per item, on the consumer's machine at a pinned, version-stamped binary — including per-tool attribution of the built-in tool pools that /context reports only as lump sums, derived live by A/B bare-name-deny differencing with enforced comparability rules…
ai-briefing
Build source-backed AI-industry briefings from official vendor publications, configured RSS/Atom feeds, GitHub releases, reputable secondary reporting, and user-supplied URLs. Deduplicate, rank, and present results as markdown or optional HTML/PPTX decks, with repository-owned profile, audience, and brand…
bugs
Produces a structured five-field bug report — title, steps to reproduce, expected vs actual, severity with justification, and suggested fix location — from an informal defect description. Read-only by default: it emits the report and never edits code, opens a PR, or files an issue on its own.