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/shopwareLabs/ai-coding-toolsWrote 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/shopwarelabs/ai-coding-tools/contributor-writing)<a href="https://agentmods.dev/plugins/shopwarelabs/ai-coding-tools/contributor-writing"><img src="https://agentmods.dev/badge/plugins/shopwarelabs/ai-coding-tools/contributor-writing/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/shopwarelabs/ai-coding-tools/contributor-writing"><img src="https://agentmods.dev/badge/plugins/shopwarelabs/ai-coding-tools/contributor-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 1mo 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 it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 745 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.
- 1mo ago First seen · 11 lines scan A a1d2e71aa45d
contributor-writing is a plugin published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 4d 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-08-30.
Other plugins, from other repositories
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
git
Git workflow automation (commit, PR, branching, changelog).
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
git
Version-control skills for the whole branch lifecycle: committing, worktrees, merge conflicts, undo/recovery, PR descriptions, changelogs, releases, and branch cleanup.
dev-workflow
Everyday dev commands -- commit, review, test, fix bugs, create PRs, check repo status, and inspect PR health. Hook: auto-format.
release-conductor
Owns everything around the diff: craft Conventional Commits and PR descriptions, recommend the right semver bump by reasoning about behavioral breaking changes, assemble changelogs from messy history, and guide merge-conflict resolution, rebase planning, and git-history archaeology.