What is verify-pi-lens?

A verification workflow for pi-lens, using its real tool interface to check language-server diagnostics, code formatting, review graphs, and file renaming. It uses Pyrefly, a Python language server, and keeps test data in a controlled temporary environment.

Use it to verify fixes or reviews in pi-lens, including Python diagnostics, formatting, review data, and rename operations.

It tests the built program through the real execution path rather than mocks, producing evidence that the features work on an actual checkout or commit.

How apmantza/pi-lens configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to apmantza/pi-lens. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/apmantza/pi-lens/master/.claude/skills/verify-pi-lens/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/apmantza/pi-lens

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/apmantza/pi-lens/verify-pi-lens/github.svg)](https://agentmods.dev/skills/apmantza/pi-lens/verify-pi-lens)

Your own site

<a href="https://agentmods.dev/skills/apmantza/pi-lens/verify-pi-lens"><img src="https://agentmods.dev/badge/skills/apmantza/pi-lens/verify-pi-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/apmantza/pi-lens/verify-pi-lens"><img src="https://agentmods.dev/badge/skills/apmantza/pi-lens/verify-pi-lens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,786 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00103	$0.01786
Opus 5.5	$0.00041	$0.00714
Sonnet 5.5	$0.00021	$0.00357
Haiku 4.5	$0.00010	$0.00179

Measured 9d ago against content hash 826f6eb87a84, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify-pi-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 9d ago.

The scan reads SKILL.md. This mod also ships 10 executable files (scripts/env.sh, scripts/pyrefly-tee.sh, scripts/scenarios/fallow-lsp.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/verify-pi-lens/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verify pi-lens

Procedure only. Role rules (what a reviewer or fixer must prove, and how) live in docs/pi-lens-reviewer.md, docs/pi-lens-fixer.md and docs/pi-lens-subagent.md; on any conflict they win. This skill replaces probes rebuilt per lane, which vanished with the worktree (#4359).

Shape after the create-verification-skill pattern: Launch, Doctor, Drive, Evidence, Cleanup, Helpers, and a features map.

Launch

Linux only (pid tracking reads /proc; verify.mjs exits 2 elsewhere), with node, git and uv. Everything a run writes lands under the lane TMPDIR; env.sh refuses /tmp.

export TMPDIR=~/.local/share/pi-lens-orchestrator/tmp/<lane>-tmp
S="$(git rev-parse --show-toplevel)/.claude/skills/verify-pi-lens/scripts"   # absolute
npm run build                      # the tree under test must be built
$S/setup.sh pyrefly                # once: Pyrefly 1.3.2 + ruff venv (py-venv)
. $S/env.sh                        # pins HOME, PI_LENS_HOME, PILENS_DATA_DIR, XDG, uv cache

env.sh sets RUN (disposable) and EVIDENCE (kept). Repeat the S= and . $S/env.sh lines in every shell call: agent shells reset their environment between calls.

The server under test is the real stdio MCP server, mcp/server.js, launched inside the scenario workspace as a host would. To verify a commit other than the checkout (the base, or the commit before a fix), build it first and pass it as --tree:

OLD=$($S/setup.sh tree <rev>)      # git archive + build under $VERIFY_ROOT/trees

Doctor

node $S/verify.mjs doctor --tree "$PWD"      # or --tree "$OLD"

Read-only on the tree. It checks the env pins, that the compiled twins are not older than their sources, that the Pyrefly venv exists, that tools/list serves the driven tools, and that pilens_health answers with tree-sitter available and no degradations or broken servers. Alive is not usable: do not drive past a FAIL.

Drive

node $S/verify.mjs drive <scenario> [variant] --tree "$PWD"

Read the full file on GitHub · 137 lines

Files

What ships with it

16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

9d ago Changed · +1 lines 826f6eb87a84
21d ago Changed · +1 lines · +6 tokens per session e5d7b58f1b2d
24d ago First seen · 135 lines · 97 tokens per session scan A 6a3807bcc95a

Subscribe to this mod's changes

verify-pi-lens is a skill published in the GitHub repository apmantza/pi-lens (514 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,786 once invoked, about $0.0004 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-10-14.

Debugging Testing

verify-pi-lens next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
verify-pi-lensapmantza/pi-lens	Skill	514	yesterday	MIT	A	103	Claude Code
systematic-debuggingopen-metadata/OpenMetadata	Skill	16k	yesterday	Apache-2.0	A	37	Claude Code
log-error-digestzebbern/claude-code-guide	Skill	4.7k	3d ago	MIT	A	71	Claude Code, Codex
cwv-optimizeradobe/skills	Skill	319	yesterday	Apache-2.0	A	112	Claude Code
ci-fixersipyourdrink-ltd/bernstein	Skill	1.2k	yesterday	Apache-2.0	A	15	Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skills	Skill	1.9k	23d ago	MIT	A	36	Claude Code
triaging-web-analytics-supportPostHog/posthog	Skill	41k	yesterday	none	A	151	Claude Code, Codex

pi-lens: Skill for Claude Code