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.
npx skills add lambdalisue/cclens --skill doctorgit clone --depth 1 https://github.com/lambdalisue/cclensWrote 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/lambdalisue/cclens/doctor)<a href="https://agentmods.dev/skills/lambdalisue/cclens/doctor"><img src="https://agentmods.dev/badge/skills/lambdalisue/cclens/doctor/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/lambdalisue/cclens/doctor"><img src="https://agentmods.dev/badge/skills/lambdalisue/cclens/doctor.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.00067 | $0.00522 |
| Opus 5 | $0.00034 | $0.00261 |
| Sonnet 5 | $0.00013 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
doctor 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 6d 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
cclens doctor — usage health check
Run cclens over the user's Claude Code transcripts and config, then present the
one-screen health check. Everything runs locally and read-only over
~/.claude; nothing is sent anywhere.
1. Resolve the binary
- Binary: use
cclensifcommand -v cclensfinds it. Otherwise run every command below through Nix instead:nix run github:lambdalisue/cclens -- <subcommand …>. If neithercclensnornixis available, stop and tell the user how to install it (nix profile install github:lambdalisue/cclens, orcargo install --git https://github.com/lambdalisue/cclens).
Omit --db everywhere: the store defaults to a per-user path
(${XDG_STATE_HOME:-~/.local/state}/cclens/cclens.db), so nothing is dropped
into the current project.
2. Report
cclens doctor
doctor refreshes the store automatically (incremental; fast when current)
and prints a freshness line on stderr. If the user asked about one layer, add
--scope global or --scope project:<slug>. (doctor has a --format json for machine use, but present the default text form.)
3. Present
Relay the report's findings in the conversation language, keeping its structure
— it is split into a global section (fix in ~/.claude) and per-project
sections (fix in each project's own config) precisely because those are
different tasks; do not merge them back together. Preserve the caveats it
prints (estimated tokens, evaluation windows); they exist so numbers are not
over-trusted. Do not pad it with generic advice.
Close by naming the follow-ups: /cclens:optimize to investigate and fix the
findings, /cclens:query for any specific slice the report does not show.
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.
- 6d ago Changed · -5 lines dbe8a30eff8f
- 9d ago First seen · 50 lines · 67 tokens per session scan A 01eca09caa3d
doctor is a skill published in the GitHub repository lambdalisue/cclens (87 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 522 once invoked, about $0.0003 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…