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/Tiltely/lensWrote 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/tiltely/lens/lens)<a href="https://agentmods.dev/plugins/tiltely/lens/lens"><img src="https://agentmods.dev/badge/plugins/tiltely/lens/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/tiltely/lens/lens"><img src="https://agentmods.dev/badge/plugins/tiltely/lens/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 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": "lens",
"version": "0.10.0",
"description": "Socratic lenses for software engineering: question batteries that examine your work from security, design, usability, test-quality, and operational-recovery perspectives — plus an orchestrator that surfaces caveats, rabbit holes, and blast radius before you build, and a memory loop that grows new lenses from your real sessions.",
"author": { "name": "Tiltely", "email": "[email protected]", "url": "https://www.tiltely.com" },
"homepage": "https://github.com/Tiltely/lens",
"repository": "https://github.com/Tiltely/lens",
"license": "MIT",
"keywords": ["socratic", "lenses", "design-review", "security", "usability", "tdd", "observability", "questions"]
}
What it installs
The manifest is a name and a version. 11 skills, 1 hook travel with it, and installing the plugin installs all of them — 825 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill socratic A 111 tokens
- Skill observability A 80 tokens
- Skill tdd A 86 tokens
- Skill design A 90 tokens
- Skill security A 68 tokens
- Skill adversary A 98 tokens
- Skill new A 44 tokens
- Skill usability A 68 tokens
- Skill retro A 60 tokens
- Skill [object Object] A 40 tokens
- Skill setup B 80 tokens
- Hook SessionEnd 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 · 11 lines scan A 89183814710f
lens is a plugin published in the GitHub repository Tiltely/lens (5 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-31.
Other plugins, from other repositories
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
pedantic-coder
Zero-tolerance code pedantry — naming precision, casing law, structural symmetry, import discipline, and the obsessive details that separate clean code from correct code.
ai-infra-auto-driven-skills
Agent-ready playbooks for LLM serving benchmarks, SGLang model Day-0 support, capacity planning, profiling, code review, incidents, PR-history dossiers, and SGLang PR/article explainer videos.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
coderabbit
CodeRabbit integration for Claude Code - local code review and PR comment management.