20,069 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Handle software testing in a test-owner style, including early test strategy, complete testing framework design, requirements analysis, test planning, manual functional testing, defect report writing, API testing, API automation regression planning, Web UI automation planning, performance testing, system acceptance…
Use when you need to run MintMaker controller code locally against a real Kubernetes cluster (minikube or kind) with repo hosted on GitHub, create test Component/DependencyUpdateCheck resources, and iterate quickly across macOS and Linux.
Use Stet to measure whether an AI coding change is safe to ship. Trigger on model comparisons, AGENTS.md or CLAUDE.md effectiveness, shared instruction, policy, skill, harness, tool-policy, reasoning, or runtime rollouts, repo eval setup, dataset building, regression detection, benchmarking, promote/rollback…
TDD-focused implementation agent. Enforces strict RED → GREEN → VALIDATE → REFACTOR cycle. Works with or without plan files. Delegates specialized work to subagents.
Use this skill when investigating, adding, validating, or debugging external website profiles for the 99idea Playwright browser demo. It teaches how to probe selectors, classify failure modes, add config-driven profiles, and validate both heuristic and Gemini flows.
Analyzes test files (.test.ts) to generate code-slice.json specification files. These capture behavioral contracts in given/when/then form, enabling drift detection between tests and slice.json design documentation.
Use when implementing features, fixing bugs (including P0 hotfixes and production incidents), refactoring, removing dead code, or deleting legacy paths. Use when user mentions TDD, red-green-refactor, test-first, or when tempted to write code before tests. Use when fixing any bug — even trivial ones. Use when…
Analyze Sui Move test coverage, identify untested code, write missing tests, and perform security audits. Includes Python tools for parsing coverage output and generating reports.
Produces practical, risk-based testing guidance and minimal test plans for features or changes. Use when user asks what to test, how to pick test cases (boundaries, permissions, state machines), how to improve weak tests, or to review existing tests. Covers equivalence partitions, boundary values, decision tables, and…
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
Implements enterprise-grade testing strategies for .NET applications using xUnit, Moq, FluentAssertions, and WebApplicationFactory. Use when writing unit tests, integration tests, or API tests in .NET or C#, configuring test projects, deciding what to mock vs what to test with real dependencies, setting up shared test…
Sauce Labs VDC capability authoring skill for desktop and virtual devices. Use when asked to generate or validate W3C/Appium capabilities for Sauce Labs.
Use this subagent to write or update test case documents under docs/Test-Case/ / and the matching automation scripts inside whatever test directory already exists under code/. Two modes — audit-driven (decision = add / skip / rewrite): each TC is derived from the PRD's business process + key page functions, assigned a…
MCP server for AI-driven API testing — HTTP, GraphQL, WebSocket, OAuth2, assertions, chained test suites, and SQLite-persisted history with JSON diff comparison. Runs locally from the @bencibro/postmcp npm package.
★not rated 5 18d agoA
tokens not measured
originalMIT
QA artifact generator — point it at a PR or give freeform instructions. Navigates the UI, captures screenshots, and stitches a GIF. Fully configurable auth and artifact storage via /.sentinel/config.json.
★not rated 5 5mo agoA
tokens not measured
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: