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/dev-tooling)<a href="https://agentmods.dev/plugins/shopwarelabs/ai-coding-tools/dev-tooling"><img src="https://agentmods.dev/badge/plugins/shopwarelabs/ai-coding-tools/dev-tooling/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/dev-tooling"><img src="https://agentmods.dev/badge/plugins/shopwarelabs/ai-coding-tools/dev-tooling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dev-tooling 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 4d 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": "dev-tooling",
"version": "4.1.1",
"description": "Three MCP servers for PHP and JavaScript operations. PHP (php-tooling): PHPStan, ECS, Rector, PHPUnit, PHPUnit coverage gap analysis, Symfony Console. Administration (js-admin-tooling): ESLint, Stylelint, Prettier, Jest, TypeScript, Vite builds. Storefront (js-storefront-tooling): ESLint, Stylelint, Jest, Webpack builds. Includes SessionStart hook that injects MCP tool directives and PreToolUse hooks that enforce MCP tool usage by blocking bash commands. Supports native, Docker, Docker Compose, Vagrant and DDEV environments.",
"author": {
"name": "Shopware Labs"
},
"license": "MIT",
"keywords": ["php", "javascript", "phpstan", "ecs", "rector", "phpunit", "eslint", "stylelint", "prettier", "jest", "typescript", "vite", "webpack", "mcp", "hooks", "static-analysis", "testing", "code-quality", "linting", "shopware", "twig"],
"homepage": "https://github.com/shopwareLabs/ai-coding-tools/tree/main/plugins/dev-tooling",
"repository": "https://github.com/shopwareLabs/ai-coding-tools"
}
What it installs
The manifest is a name and a version. 1 agent travel with it, and installing the plugin installs all of them — 141 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.
- 4d ago Changed 162f39eb750c
- 7d ago Changed 52483cc41db0
- 29d ago Changed 014d5aa66824
- 1mo ago Changed fbdde5de6ba5
- 1mo ago First seen · 13 lines scan A f2dddb9ec016
dev-tooling 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
implementation
Disciplined implementation stage: execute approved plans inline (/implementation:implement) or via orchestrated worker subagents (/implementation:implement-dispatch) with incremental validation, TDD-by-default cadence, green-checkpoint commits, scope-fence drift detection, and divergence detection that routes back.
evals
LLM evaluation methodology and eval-suite design, based on Anthropic's evaluation guidance. /evals:methodology answers questions on success criteria, eval design, and grading. /evals:design interviews for measurable success criteria and scaffolds a graded eval suite for an LLM app or Claude Code skill.…
mutation-testing
Measures whether a test suite can actually detect faults, not merely execute code: /mutation-testing:principles answers operator, mutant-state, and metric questions from the primary literature; /mutation-testing:setup verifies the ecosystem's mutation tool and writes the tracked config; /mutation-testing:audit ru.
playwright
Live E2E browser automation via Microsoft's @playwright/cli: named sessions, accessibility-ref snapshots, click/fill by ref, screenshots, console and network capture, mocking, tracing, video, and auth state, with artifacts written to disk so only paths enter context, plus a vendored upstream baseline and maintainer…
code-metrics
Read-only code measures for a change, with cited references and no verdict: lines per file (audit-size), cyclomatic, cognitive, and Halstead complexity (audit-complexity), duplication (audit-duplication), per-function coverage and CRAP from existing lcov, Cobertura, coverage.py, or Go artifacts (audit-coverage)…
debugging
Debug observed failures via a disciplined six-phase loop: build a fast deterministic reproduction signal, reproduce, rank falsifiable hypotheses, instrument, fix with a regression test, then clean up and post-mortem.