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/Karzone/TestAtlasWrote 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/karzone/testatlas/claude-plugin)<a href="https://agentmods.dev/plugins/karzone/testatlas/claude-plugin"><img src="https://agentmods.dev/badge/plugins/karzone/testatlas/claude-plugin/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/karzone/testatlas/claude-plugin"><img src="https://agentmods.dev/badge/plugins/karzone/testatlas/claude-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
testatlas 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 11d 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": "testatlas",
"displayName": "TestAtlas",
"version": "0.1.3",
"description": "A queryable map of your .NET test-automation solution for Claude: find existing steps before writing new ones, trace the blast radius of a change, and keep the map fresh. Needs the .NET 8 SDK and two global tools (dotnet tool install --global TestAtlas.Cli / TestAtlas.Mcp); the plugin tells you when they are missing.",
"author": {
"name": "Karzone",
"url": "https://github.com/Karzone"
},
"homepage": "https://github.com/Karzone/TestAtlas",
"repository": "https://github.com/Karzone/TestAtlas",
"license": "MIT",
"keywords": [
"dotnet",
"testing",
"reqnroll",
"specflow",
"gherkin",
"mcp",
"test-automation",
"code-analysis"
]
}
What it installs
The manifest is a name and a version. 3 skills, 1 hook, 1 MCP server travel with it, and installing the plugin installs all of them — 248 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 11d ago Changed efab87bd51a1
- 13d ago Changed · +12 lines 9d54b0bebf48
- 20d ago First seen · 12 lines scan A 950780299ec1
testatlas is a plugin published in the GitHub repository Karzone/TestAtlas (3 stars, last pushed 6d 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-27.
Other plugins, from other repositories
unit-test
Scenario-based functional test orchestrator: git-diff scoping, storyboard generation, test-case creation, Playwright MCP execution, and a PASS/FAIL/WARN report.
e2e
E2E test triage, debugging, and fix implementation toolkit.
meticulous
Agent skills for Meticulous visual regression testing — review test runs, investigate replays, debug diffs. Also connects the hosted Meticulous MCP server.
playwright-e2e
Author and maintain resilient Playwright end-to-end tests using the Page Object Model, fixtures, stable user-facing locators, and web-first assertions. Enforces guardrails against flakiness, brittle selectors, and shared state. Drives Playwright's built-in planner, generator, and healer agents (playwright-test MCP)…
sniff
Autonomous QA scanner via sniff-qa: walks your running app in a real browser and reports real bugs (broken pages/links, console/network errors, broken forms, state-loss, empty/placeholder data, bad loading/error states, responsive + a11y) with reproduction proof, severity, confidence, and a fix. No API key.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.