Authoring role for the D365FO agent eval loop catalog. Drafts a new eval/cases/ .json spec (valid against eval/cases/schema.json), scaffolds its golden folder, and sets goldenpending until the golden is captured on the VM. Use when asked to "add an eval case", "author a case for ", "draft a case from this failure", or…
Implementer role of the D365FO agent eval loop. Runs ON THE VM (mcp-server in full mode + C# bridge) against the Contoso sandbox model. Takes an eval case id, drives the grounded MCP tool path to implement it, builds, scores against the golden/SysTest oracle, writes a corpus record, and rolls back. Use when asked to…
Improver role of the D365FO agent eval loop. Reads the corpus of run records, ranks failure clusters, reproduces a TOOLDEFECT/KNOWLEDGEGAP/VALIDATORGAP as a minimal VM-free repo test, fixes it, validates against the held-out split, and opens a PR citing corpus evidence. Runs in the repo (never touches the VM). Use…
QA gatekeeper for Txtify. Use to run the full verification ladder on the current tree and report evidence — before merging, releasing, or when asked "does everything still work?".
A full-repository quality review and improvement agent for a Go project. Go is a programming language, and a repository is the project folder containing its source code and supporting files.
Verifies implementation work by running code, executing tests, and generating adversarial test cases. Checks against the problem definition and principles, not against the proposal document. Approval is gated on execution results, not code reading.
Validates that the executed sprint actually meets PLAN.md's Nyquist criteria. Fills coverage gaps by writing tests for any criterion not already covered. Implementation files are READ-ONLY. Spawned by /jira:execute after jira-executor finishes.
Use this agent when you need to test n8n webhook endpoints with specific input data and verify their execution results. This agent creates bash test scripts (handling JWT tokens when needed), executes them, and cleans up afterward. Keeps test execution isolated from the main conversation context.
Tests the Oh My Posh Configurator MCP server. Use this agent to validate MCP tools like listing segments, creating configurations, validating configs, and exporting in different formats.
Verifies UI changes in the browser using playwright-cli across Blink, Gecko, and WebKit. Use after making visual or interaction changes to React components, CSS, layouts, or routing to confirm they render and behave correctly.
Use this agent when you need to write comprehensive unit tests for existing code, when implementing test-driven development, when code coverage needs improvement, or when refactoring requires test safety nets. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this…
A coding workflow for adding new Protocol Launcher tools, which open applications through special links. It creates the implementation, exports, configuration entries, and unit tests needed for a new protocol.
Validates PHPUnit test comprehensiveness and integrity. Use after code review to audit PHP/Laravel tests for cheating, TODO placeholders, insufficient coverage, or hollow assertions. Reports failures requiring developer subagent correction.
Evaluate expectations against an execution transcript and outputs.
126 3d agoA0 tokens
copy · 100%Apache-2.0
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: