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 swesmith/davila7__claude-code-templates.734b8a50npx agentmods add plugins/swesmith/davila7__claude-code-templates.734b8a50/testing-suitegit clone --depth 1 https://github.com/swesmith/davila7__claude-code-templates.734b8a50Wrote 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/swesmith/davila7__claude-code-templates.734b8a50/testing-suite)<a href="https://agentmods.dev/plugins/swesmith/davila7__claude-code-templates.734b8a50/testing-suite"><img src="https://agentmods.dev/badge/plugins/swesmith/davila7__claude-code-templates.734b8a50/testing-suite.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
testing-suite 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 today.
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": "testing-suite",
"source": "./",
"description": "Comprehensive testing toolkit with E2E, unit, integration, and visual testing automation",
"version": "1.0.0",
"author": {
"name": "Daniel Avila"
},
"license": "MIT",
"keywords": [
"testing",
"qa",
"e2e",
"automation",
"quality"
],
"strict": false,
"commands": [
"./cli-tool/components/commands/testing/generate-tests.md",
"./cli-tool/components/commands/testing/e2e-setup.md",
"./cli-tool/components/commands/testing/test-coverage.md",
"./cli-tool/components/commands/testing/setup-visual-testing.md",
"./cli-tool/components/commands/testing/setup-load-testing.md",
"./cli-tool/components/commands/testing/test-automation-orchestrator.md",
"./cli-tool/components/commands/testing/test-quality-analyzer.md"
],
"agents": [
"./cli-tool/components/agents/development-tools/qa-automation-engineer.md",
"./cli-tool/components/agents/development-tools/test-engineer.md"
],
"mcpServers": [
"./cli-tool/components/mcps/browser_automation/playwright-mcp.json"
]
}What ships with it
1 file beside marketplace.json#testing-suite in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 34 lines scan A 55b0adbf3795
testing-suite is a plugin published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo 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-09-03.
Other plugins, from other repositories
quality-skills
Quality engineering skills for QA engineers, SDETs, and test automation leads — covering frontend (Selenium/Cypress/Playwright), API (Postman/REST Assured/Karate), performance (k6/JMeter/Gatling), mobile (Appium), BDD, accessibility, visual regression, security, chaos, contract testing, CI orchestration, and quality…
testing-expert
Test strategy and implementation: unit/integration/e2e, TDD, mocking, fixtures, and coverage.
vue-testing-best-practices
Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.
testing-strategies
Unit, integration, E2E testing and TDD practices.
testing-quality-suite
Test-driven development workflows, automated test generation, test harness setup, and multi-perspective code review for unit, integration, and end-to-end testing.
testing-suite
Comprehensive testing toolkit with E2E, unit, integration, and visual testing automation.