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/soumyachk101/VibeLensWrote 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/soumyachk101/vibelens/plugin)<a href="https://agentmods.dev/plugins/soumyachk101/vibelens/plugin"><img src="https://agentmods.dev/badge/plugins/soumyachk101/vibelens/plugin/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/soumyachk101/vibelens/plugin"><img src="https://agentmods.dev/badge/plugins/soumyachk101/vibelens/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibelens 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": "vibelens",
"displayName": "VibeLens",
"description": "Gives Claude eyes on localhost. Captures a screenshot, console/network errors and a token-optimized DOM snapshot of your dev server so UI bugs get fixed from evidence instead of guesswork.",
"version": "1.0.0",
"author": {
"name": "Soumya Chakraborty",
"url": "https://github.com/soumyachk101"
},
"homepage": "https://github.com/soumyachk101/VibeLens#readme",
"repository": "https://github.com/soumyachk101/VibeLens",
"license": "MIT",
"keywords": [
"ui",
"frontend",
"debugging",
"screenshot",
"playwright",
"localhost",
"responsive"
]
}
What it installs
The manifest is a name and a version. 12 skills, 4 agents, 1 hook travel with it, and installing the plugin installs all of them — 1,329 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill layout-audit A 87 tokens
- Skill micro-interactions A 86 tokens
- Skill motion-system A 80 tokens
- Skill polish-pass A 100 tokens
- Skill color-system A 92 tokens
- Skill design-review A 107 tokens
- Skill type-system A 95 tokens
- Skill a11y-audit A 71 tokens
- Skill console-triage A 84 tokens
- Skill before-after A 61 tokens
- Skill check-ui A 50 tokens
- Skill responsive-audit A 41 tokens
- Agent frontend-builder A 121 tokens
- Agent design-reviewer A 103 tokens
- Agent ui-debugger A 74 tokens
- Agent ui-reviewer A 77 tokens
- Hook PostToolUse A not measured
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 · 23 lines scan A 25629c63943f
vibelens is a plugin published in the GitHub repository soumyachk101/VibeLens (0 stars, last pushed 18d 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
subio-scrape
Scrape public posts from X, LinkedIn, Hacker News and Reddit in a local browser that is never signed in.
devcdp
Real Chrome DevTools access for Claude: console, network, DOM, source maps, breakpoints and live variables, plus guidance on when to use each.
devcdp
Real Chrome DevTools access for Gemini CLI: console, network, DOM, source maps, breakpoints and live variables.
peekdev
Let your AI coding agent debug what already happened in your real browser. peek records masked rrweb sessions of your real browser to a local store and exposes them (DOM history, console/network errors, the action before an error, session-to-Playwright repro) to coding agents over MCP — and, with per-origin consent…
web-debug
Evidence-first local web debugging and reviewed manual-parity qualification around native test workflows.
chrome-devtools-mcp
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer.