QA engineer for unit and external API tests. Invoke to generate or maintain xUnit tests — unit tests in .Tests (routes to dotnet-test) or external API integration tests in .ApiTests (routes to dotnet-test-api). Tests only — no production code or docs.
Use this agent when you need to test n8n-mcp functionality after implementing fixes or new features. This agent should be invoked proactively after code changes to validate that the MCP tools work correctly with real n8n workflows. The agent tests the actual MCP server tools, not just unit tests. Examples:\n\n…
Smoke-tests the deployed context-kernel MCP server: auth gating, read tools, and write/journal round-trip. Use after a deploy or when the owner says "test the MCP", "check the connector", "is context-kernel up". Reports pass/fail; does not change server code or curated content.
Use this agent when you need to test n8n-mcp functionality after implementing fixes or new features. This agent should be invoked proactively after code changes to validate that the MCP tools work correctly with real n8n workflows. The agent tests the actual MCP server tools, not just unit tests. Examples:\n\n…
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
Independently verifies features in a running application against the verification steps in docs/feature-list.json. Operates in an isolated git worktree, judges outcomes only, never modifies source. Spawned by /onboard:verify.
Session integration tester. Runs the whole-project test suite and E2E once, and judges whether the session's work is actually wired into the system. Sonnet base.
Plays one AGENTIC (non-persona) QA-engineer session in a CapusQA run created with mode="agentic". Spawned in parallel for an agentic run (by the CapusQA runner / autopilot), one per session. Claims tasks, adopts the agentic behaviorcontract, and drives the app as a thorough adversarial tester — full knowledge…
Plays one human persona testing a macOS app through the capusqa MCP daemon. Spawned in parallel for a human run (by the CapusQA runner / autopilot), one per persona-session. Claims tasks from the run's work queue and drives the app via observe/click/type tools while staying in character.
Agent "n8n-mcp-tester" from mohsin-zaheer/mcp-server, covering your core responsibilities, testing methodology, testing guidelines, example test execution and important constraints.
Use this agent when you need to test n8n-mcp functionality after implementing fixes or new features. This agent should be invoked proactively after code changes to validate that the MCP tools work correctly with real n8n workflows. The agent tests the actual MCP server tools, not just unit tests. Examples:\n\n…
Use this agent when you need to create, expand, or improve test suites for code in the project. This includes writing unit tests, integration tests, and end-to-end tests. Also use this agent when new functionality has been implemented and needs test coverage, when existing tests are insufficient or brittle, or when…
Comprehensive testing specialist for ServalSheets. Designs test strategies, writes property-based tests, implements mutation testing, and ensures 100% critical path coverage. Uses TDD/BDD patterns and fast test execution. Use when adding features, fixing bugs, or improving test coverage.
Debugging specialist for failed OLTestStack browser tests. Use proactively when tests fail, elements are not found, navigation times out, or unexpected UI behavior occurs. Captures console, network, snapshot, and screenshot evidence for root cause analysis.
Specialized agent for running browser tests via OLTestStack MCP tools. Use proactively when asked to test web pages, login flows, CRUD operations, smoke tests, or UI verification. Invokes olteststack MCP tools directly — never simulates browser actions without calling MCP.
★not rated 0 2mo agoA58 tokens
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: