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/code-contribution-analysis)<a href="https://agentmods.dev/plugins/shopwarelabs/ai-coding-tools/code-contribution-analysis"><img src="https://agentmods.dev/badge/plugins/shopwarelabs/ai-coding-tools/code-contribution-analysis/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/code-contribution-analysis"><img src="https://agentmods.dev/badge/plugins/shopwarelabs/ai-coding-tools/code-contribution-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-contribution-analysis 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": "code-contribution-analysis",
"version": "1.0.1",
"description": "Skills for analyzing GitHub pull requests and issues in depth. Fetches contribution data from GitHub and researches architectural context via chunkhound-integration. Standalone useful for code review, and designed to be consumable by Claude Agent SDK applications.",
"author": { "name": "Shopware Labs" },
"license": "MIT",
"keywords": ["github", "pull-request", "issue", "code-review", "analysis", "chunkhound", "architecture", "shopware"],
"homepage": "https://github.com/shopwareLabs/ai-coding-tools/tree/main/plugins/code-contribution-analysis",
"repository": "https://github.com/shopwareLabs/ai-coding-tools"
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 107 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 b85324deec2c
code-contribution-analysis is a plugin published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 3d 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
dev-workflow
Everyday dev commands -- commit, review, test, fix bugs, create PRs, check repo status, and inspect PR health. Hook: auto-format.
delivery-suite
Publish the intended changes and verify what reached the remote repository or target environment.
review
PR review, interactive git diff annotation review, and writing style guide.
architecture
improve uses Ousterhout's deep-module lens to find shallow modules, seam leaks, and locality gaps, reports them as HTML, and interviews the chosen one. map-landscape charts a C4 system landscape and portfolio table with drift checks. map-dependencies, map-components, map-containers, map-context, map-flow, map-events…
repo-hygiene
Repo hygiene action-router: /repo-hygiene:clean sweeps reclaimable caches, build artifacts, and stale git metadata, and can realign the working tree to a fresh-pull state, dry-run-first, with destructive tiers gated behind explicit confirmation and a session-scoped destructive-command guard. Ecosystem targets are…
codebase-health
Repo-wide drift audit between docs, config, code, and architecture: verifies every factual claim against reality via parallel subagent fan-out, severity-rates findings, and reports read-only, delegating remediation to the implementation/verification lanes. Audit dimensions are configurable through a tracked…