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.
npx agentmods add plugins/indate/devharness/plugin/plugin marketplace add InDate/devharnessgit clone --depth 1 https://github.com/InDate/devharnessGrade A, and why
devharness 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 yesterday.
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": "devharness",
"description": "Run and debug a live app from inside Claude Code: breakpoints and variable inspection in Chrome and Node.js, managed dev servers, and replayable call history so setup is never re-driven by hand.",
"author": {
"name": "InDate",
"url": "https://github.com/InDate"
},
"homepage": "https://github.com/InDate/devharness",
"license": "MIT"
}
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.
- yesterday First seen · 11 lines scan A c44b6231663c
devharness is a plugin published in the GitHub repository InDate/devharness (16 stars, last pushed yesterday), 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-08-30.
Other plugins, from other repositories
mochi
A browser companion for AI assistants. Bundled MCP tools for Chrome automation, persistent project memory (Continuum chain), and an in-page hint modal — pair with the Mochi Chrome extension.
mochi
Mochi — a browser companion for AI assistants. Bundled browser automation, persistent project memory, and human-in-the-loop hint messaging.
tandem
A shared Chrome browser (human + Claude, CDP + Playwright MCP) that learns how each site is navigated: the human drives with the mouse and clears captchas/logins, Claude operates over CDP, and tandem:map persists per-site navigation memory (durable locators, drift, auto-injection).
quimera-ai
Claude Code plugins by bgmacris. Currently: tandem — a real-time shared Chrome (human + Claude, CDP + Playwright MCP) with per-site navigation memory.
chrome-multi-instance-warn
An agent driving a browser tends to start a new one rather than use the one already open, and to size its work off the core count. This warns once per session when a tool payload is about to do either. Never blocks.
didvc-browser-plugins
Small, single-purpose Claude Code plugins focused on staying out of the machine's way.