Claude Code mod
test-radar
Runs the tests related to each change (Claude's edits and yours) in the background; a failure caused by Claude's edit reaches Claude mid-turn, and the band offers Show and Fix it.
Install
/plugin marketplace add mako-code/gobworks
/plugin install test-radar@gobworksMods install like plugins. Run /reload-plugins or start a new session to load it.
What it can access
- Reach
- L2Writes or runs: runs processes, writes files, drives Claude, reads files, reads env vars, reads mod state, persists state, draws
- Sees
- every tool call, every prompt
- Draws in
AbovePromptPane- Hooks
session.starttool.callturn.startturn.completeprompt.submitsession.endcommand.runui.render
From a static scan of the mod's code by awesome-claude-code-mods. It shows what the code asks for, not a security review.
How Claude Code mods work
- A mod is a plugin with a JavaScript or TypeScript module that runs inside Claude Code (version 2.1.287 or later). It can draw panes beside the transcript, a band above the prompt, buttons and toasts, restyle the spinner and tool rows, and watch or rewrite tool calls and prompts.
- It installs like any plugin: add its marketplace with /plugin marketplace add owner/repo, then /plugin install name@marketplace.
- Check what a mod can reach before installing: it runs with your permissions. Reach goes from drawing only, to reading files, to writing files or running processes, to the network. Run claude plugin validate on a clone to list its hooks and calls without running it.
- Turn one off from the Installed tab in /plugin, or start Claude Code with --safe-mode to skip every customization for a session.
Details
- Repository
- mako-code/gobworks
- Folder
mods/ambient/test-radar- Marketplace
gobworks- Author
- mako-code
- License
- MIT
- Last updated
- 4 October 2026
- Listed in
- awesome-claude-code-mods
FAQ
What is test-radar?
Runs the tests related to each change (Claude's edits and yours) in the background; a failure caused by Claude's edit reaches Claude mid-turn, and the band offers Show and Fix it. It is a mod for Claude Code, from mako-code/gobworks on GitHub.
What can the test-radar mod access?
Its widest reach is "writes or runs" (runs processes, writes files, drives Claude, reads files, reads env vars, reads mod state, persists state, draws). It sees every tool call, every prompt. It draws in AbovePrompt, Pane. Like any mod, it runs with your permissions.
How do I install test-radar?
Inside Claude Code (v2.1.287 or later), run /plugin marketplace add mako-code/gobworks and then /plugin install test-radar@gobworks.
Is test-radar popular?
mako-code/gobworks has 2 GitHub stars and 0 forks, and is included in 1 curated Claude Code list. It was last updated on 4 October 2026.
More pane & dashboard mods
swarm
2mako-code/gobworks
Splits a task into independent parts, runs them as parallel subagents you launch and watch live, then hands their results back for integration.
tool-diet
2mako-code/gobworks
See which tools fill the prompt, grouped by MCP server, and move them behind ToolSearch (or pin them in) per project.
subagent-monitor
2mako-code/gobworks
Every subagent, live: a /subagents pane with status, model, elapsed time, steps, tokens, last tool and answer, plus a band while any run.
tool-stopwatch
2mako-code/gobworks
Tool latency: times every tool call, shows a live timer for slow ones, and a /stopwatch pane with per-tool averages, p95, max and the slowest calls.
stub-detector
2mako-code/gobworks
No lazy placeholders: flags TODOs, '... rest of code', NotImplemented stubs and empty bodies an edit introduces, nudges Claude to finish them, and lists what is left.
verify-loop
2mako-code/gobworks
Runs your project's checks after Claude edits, shows pass/fail above the prompt, and closes the loop with one-press (or automatic, bounded) fixes.
Browse the most popular Claude Code mods, all pane & dashboard mods, or the skills and MCP server directories.