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.
git clone --depth 1 https://github.com/KaichenCurry/TabNexusWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/kaichencurry/tabnexus/claude-code)<a href="https://agentmods.dev/plugins/kaichencurry/tabnexus/claude-code"><img src="https://agentmods.dev/badge/plugins/kaichencurry/tabnexus/claude-code/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/kaichencurry/tabnexus/claude-code"><img src="https://agentmods.dev/badge/plugins/kaichencurry/tabnexus/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tabnexus 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 1mo 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.
What it actually says
{
"name": "tabnexus",
"version": "1.0.5",
"description": "Search, manage, and edit TabNexus workspaces and Chrome tabs from Claude Code.",
"author": {
"name": "TabNexus"
}
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 9 lines scan A e114dd8c617b
tabnexus is a plugin published in the GitHub repository KaichenCurry/TabNexus (3 stars, last pushed 2mo 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-30.
Other plugins, from other repositories
full-self-browsing
Connect Grok Bot to Full Self Browsing on its own computer for supervised browser actions, DOM reads and application capabilities.
browser-relay
Let agents use the Chrome you already have open and logged in through a Skill + CLI, locally or across machines.
vaaya
Pay for APIs and buy supported tokenized shares with prepaid funds. Search, research, media, data, compute and more through one Vaaya account. Agent purchase and Instinct funding guide: https://vaaya.ai/llms.txt.
chrome-bridge
Borrow a tab from your own logged-in Chrome and hand it back: navigate, read, fill, audit, diff and record in the browser you already use; logins, 2FA and CAPTCHAs stay with you (handoff). ChromeOS included; the debugger only on request (trusted input, traces, video). Ships the chrome-bridge skill (recipes) and the…
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.
mcp
Read, write, search, and manage your Kept conversation vault.