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.
/plugin marketplace add TueJon/webmcpifynpx agentmods add plugins/tuejon/webmcpify/marketplacegit clone --depth 1 https://github.com/TueJon/webmcpifyGrade A, and why
webmcpify 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 2d ago.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- webmcpify — 86% identical, 14 lines differ
What it actually says
{
"name": "webmcpify",
"owner": {
"name": "Jonas Tüchler"
},
"plugins": [
{
"name": "webmcpify",
"source": "./",
"description": "WebMCP agent skill for curated core coverage or route-by-route parity — inventory an existing web app, integrate approved tools, then verify and heal them in a real browser.",
"version": "0.5.0"
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 15 lines scan A de0e67c16c38
webmcpify is a plugin published in the GitHub repository TueJon/webmcpify (6 stars, last pushed 3d ago), 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-31.
Other plugins, from other repositories
chrome-devtools-plugins
Bundled plugins for actuating and debugging the Chrome browser.
chrome-devtools-mcp
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer.
nekuda
nekuda's Claude Code plugins, including WebMCP Kit.
webmcp-kit
Add WebMCP tools to a web app: read the repo, propose a reviewable tool plan, implement against @nekuda/webmcp-sdk, and verify the tools in a browser.
claude-in-chrome
Drive your real, logged-in Chrome from Claude Code, and list tabs across readable Chrome and Chromium profiles. Exposes the extension's browser tools through the Claude in Chrome bridge and adds a read-only listopentabs tool backed by local session data. Driving requires the connected extension and a running Chrome.
agentos-chrome-cdp
Control exact logged-in Chrome profiles with a Codex-compatible browser API.