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/ApurvBazari/claude-pluginsWrote 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/apurvbazari/claude-plugins/lens)<a href="https://agentmods.dev/plugins/apurvbazari/claude-plugins/lens"><img src="https://agentmods.dev/badge/plugins/apurvbazari/claude-plugins/lens/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/apurvbazari/claude-plugins/lens"><img src="https://agentmods.dev/badge/plugins/apurvbazari/claude-plugins/lens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lens 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 today.
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": "lens",
"version": "1.5.2",
"description": "Intent-grounded review companion — checks the session diff against spec & plan, verifies findings, renders a review.",
"author": { "name": "Apurv Bazari" },
"repository": "https://github.com/ApurvBazari/claude-plugins",
"license": "MIT",
"keywords": ["code-review", "pr-review", "intent-grounded", "adversarial-verification", "interactive-html"]
}
What it installs
The manifest is a name and a version. 4 skills, 6 agents travel with it, and installing the plugin installs all of them — 638 tokens a session between 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.
- today Changed 7963e35672ab
- 1mo ago Changed c6b691fe1a40
- 1mo ago First seen · 10 lines scan A f1f448b75b6f
lens is a plugin published in the GitHub repository ApurvBazari/claude-plugins (2 stars, last pushed yesterday), 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
clean-room
Carves safety-adjacent requests into a safe scope, executed by a genuinely isolated fresh-context subagent, with an adversarial verify pass and a descope ledger.
doc-drift
Audits the memory and documents Claude Code loads into context (CLAUDE.md, MEMORY.md, skills, agents, commands, plugins) for outdated claims, contradictions, risky/ambiguous wording, and session-only leakage. Produces a prioritized report at .drift-reports/.
freeze
Declare the editable zone — everything outside is frozen. Prevents scope creep during implementation by locking untouched files.
integration-intake
5-item screening gate for adopting external patterns (skills/agents/rules/plugins/MCP), with a provenance/injection check for imported executable content.
project-init
Interview-based project scaffolding for Claude Code — generates CLAUDE.md, ROADMAP, .gitignore, and .env.example from decisions, not templates.
scope
Define what is IN, what is OUT, and exit criteria before implementation. Quick mode (3 questions) or Full mode (layered spec with ADR).