Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Tiltely/lens/plugin install 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/skills/tiltely/lens/new)<a href="https://agentmods.dev/skills/tiltely/lens/new"><img src="https://agentmods.dev/badge/skills/tiltely/lens/new/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/skills/tiltely/lens/new"><img src="https://agentmods.dev/badge/skills/tiltely/lens/new.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00044 | $0.01067 |
| Opus 5.5 | $0.00018 | $0.00427 |
| Sonnet 5.5 | $0.00009 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
new 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Lens Scaffolder
Every lens — bundled or one you create — is used the same way: through
/lens:socratic, which discovers and applies it. Lenses you create are NOT separate
slash commands; only the bundled set has /lens:<name> shortcuts (a Claude Code
namespace limit, not a choice). So a new lens just needs a HOME + a registry row that
socratic reads. Draft the battery socratically first (step 3), then write it to the
chosen scope — no commit, no plugin rebuild, no reload; socratic reads it fresh.
Offer the SCOPE — but only the options that apply to the current context (never ask about "maintaining the plugin"; that option appears on its own, below, only when you detect you're inside the lens plugin repo):
- Project — applies only in THIS repo (when cwd is in a git repo). Write to
<repo>/.lens/lenses/<name>/SKILL.mdfrom the template (no surviving placeholders), append the row to<repo>/.lens/registry.md(create if absent), and git-exclude.lens/viagit rev-parse --git-path info/exclude(handles worktrees/submodules; on failure PROPOSE a.gitignoreentry — never silently edit it). To SHARE it with the team, commit its SKILL.md to<repo>/.claude/skills/lens-<name>/(Claude Code loads that one natively as a slash command). - Global — applies everywhere on this machine. Write to
<foundry>/lenses/<name>/SKILL.mdand append the row to<foundry>/registry.md(foundry from the config:$LENS_CONFIG→~/.claude/lens.json→~/lens/lens.json). Lives in the foundry, outside the plugin — auto-updates never touch it. A global lens that earns its keep can be PR'd into the bundled set. - No foundry config and not in a repo: write the drafted lens to
./lens-proposal-<name>.mdwith a note on how to add it later, and point at /lens:setup.
Maintainer path — auto-detected, never asked. Offer "into the bundled set" ONLY
when the current git repo IS the lens plugin itself — detect it: the repo root
(git rev-parse --show-toplevel) contains .claude-plugin/plugin.json whose name
is lens. That is the only signal; there is no pluginRepo config and no setup
question. If detected, the steps below apply (the plugin repo is the cwd's repo root).
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 · 65 lines · 44 tokens per session scan A 02e781629d97
new is a skill published in the GitHub repository Tiltely/lens (5 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,067 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.