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 TechGardenCode/naive-usernpx agentmods add plugins/techgardencode/naive-user/marketplacegit clone --depth 1 https://github.com/TechGardenCode/naive-userGrade A, and why
naive-user 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": "naive-user",
"owner": { "name": "Kian Alikhani" },
"plugins": [
{
"name": "naive-user",
"source": "./",
"description": "Drive a live web app as a source-blind, naive first-time user and report UX/behavior gaps before deploy. Config-driven, Playwright-MCP powered."
}
]
}
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.
- yesterday First seen · 12 lines scan A a48aafba2566
naive-user is a plugin published in the GitHub repository TechGardenCode/naive-user (1 stars, last pushed 1mo 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
browser-harness
Direct browser control via CDP. Drives the user's real Chrome (or a Browser Use cloud browser) with coordinate clicks, screenshots, and Python helpers — no selector hunting. Requires the one-time browser-harness CLI install (see the skill's references/install.md).
cli
Run HeadlessX website, search, YouTube, and jobs workflows from the terminal.
frane-vibesurfer
vibesurfer (vs) — agent-native headless browser.
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).
ghostlight
Governed, semantic tools for driving the user's real browser: navigate, inspect, find, click, fill, type, screenshot, record. Local by construction, with optional policy and audit.
sylin-org-plugins
Plugin marketplace listing 1 plugin: ghostlight.