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 treesoop/claude-native-pluginnpx agentmods add plugins/treesoop/claude-native-plugin/marketplacegit clone --depth 1 https://github.com/treesoop/claude-native-pluginGrade A, and why
treesoop-plugins 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
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "treesoop-plugins",
"owner": {
"name": "Treesoop",
"email": "[email protected]"
},
"metadata": {
"description": "Claude Code plugins that save tokens and money by Treesoop",
"version": "1.0.3",
"pluginRoot": "./plugins"
},
"plugins": [
{
"name": "playwright-optimizer",
"description": "Reduce Playwright MCP token usage by ~90% using Haiku summarization",
"source": "./plugins/playwright-optimizer",
"category": "optimization",
"tags": ["playwright", "token-optimization", "browser", "haiku", "cost-reduction"]
},
{
"name": "task-tracker",
"description": "Track Claude Code usage (tokens, time, projects) per team member",
"source": "./plugins/task-tracker",
"category": "analytics",
"tags": ["usage-tracking", "tokens", "team", "analytics", "supabase"]
}
]
}
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 · 30 lines scan A b191188d40bd
treesoop-plugins is a plugin published in the GitHub repository treesoop/claude-native-plugin (2 stars, last pushed 4mo 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
cli
Run HeadlessX website, search, YouTube, and jobs workflows from the terminal.
hhru
Plugin marketplace listing 1 plugin: hhru-cc-plugin.
dhm
Plugin marketplace listing 1 plugin: dear-hiring-manager.
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
webmcpify
Plugin marketplace listing 1 plugin: webmcpify.
realbrowser
Target-first local Chrome/Chromium browser control with signed-in profiles, labeled tabs, and guarded actions.