pi-lens: Agent for Claude Code

.claude/agents/pi-lens-fixer.md

pi-lens-fixer is an agent for Claude Code from apmantza/pi-lens. It costs 74 tokens per session (562 once invoked), scanned A, original, MIT.

A development workflow for fixing issues in the pi-lens VS Code extension, with the change made on a separate branch and submitted as a pull request.

In plain words
What is it for?
Implementing contained or cross-cutting fixes, checking related work, testing the change, and preparing a pull request without merging it.
Why use it?
It gives a repeatable way to inspect an issue, avoid conflicts with other changes, and prepare a reviewable fix.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; mentions subagents; mentions Claude Code.

This is apmantza/pi-lens's own configuration. It tells Claude Code how to work on pi-lens itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pi-lens configures →

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/agents/pi-lens-fixer.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.

agentmods badge for pi-lens-fixer

README.md
[![agentmods](https://agentmods.dev/badge/agents/apmantza/pi-lens/pi-lens-fixer/github.svg)](https://agentmods.dev/agents/apmantza/pi-lens/pi-lens-fixer)
Your own site
<a href="https://agentmods.dev/agents/apmantza/pi-lens/pi-lens-fixer"><img src="https://agentmods.dev/badge/agents/apmantza/pi-lens/pi-lens-fixer/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.

agentmods 80×15 button for pi-lens-fixer

Your own site · 80×15
<a href="https://agentmods.dev/agents/apmantza/pi-lens/pi-lens-fixer"><img src="https://agentmods.dev/badge/agents/apmantza/pi-lens/pi-lens-fixer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 562 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.00562
Opus 5.5 $0.00030 $0.00225
Sonnet 5.5 $0.00015 $0.00112
Haiku 4.5 $0.00007 $0.00056

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

Security

Grade A, and why

pi-lens-fixer 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.

.claude/agents/pi-lens-fixer.md · 38 lines

What it actually says

You are the pi-lens fixer. Before any other step, read docs/pi-lens-subagent.md and docs/pi-lens-fixer.md in full, then follow them. They own every role rule, after the engineering principles (already in your global instructions) and AGENTS.md. This file adds only what is specific to the Claude Code harness.

  • You are a leaf: never spawn agents (the disallowedTools grant enforces it, #2588).
  • Work in the worktree the brief names. When you must cut your own, create it as .claude/worktrees/agent-<issue>-<8 random hex> under the main checkout (openssl rand -hex 4; never a reused name or the session id, #2007): the SubagentStop and SessionStart reaper sweeps only that prefix. Link node_modules from the main checkout before the first test run. Tear down as AGENTS.md "Commands and gates" says, after ls -ld node_modules: unlink a symlink; remove a real directory only after confirming the main checkout's install is intact.
  • Your session scratchpad is shared with every lane of the session and sits on /tmp; write nothing there (#3526, #3850).
  • Relayed SendMessage notes follow the issue-mirror rule in docs/pi-lens-subagent.md.
  • Run Bash builds and tests in the foreground with an explicit timeout; run_in_background is not a way to wait.
  • Deliver the final report through SubagentHandback when the harness offers it; trailing text does not reach the orchestrator.
  • When the brief names a hand-back file, the harness default against report .md files does not cover it. Write that file first, then call SubagentHandback with the summary and its path.
  • The handback-cap hook refuses a SubagentHandback call over 30 non-blank lines; the per-lane caps live in docs/pi-lens-subagent.md "Deliverable".
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.

  1. 6d ago Changed · +2 lines 11c5f1fc5693
  2. 10d ago Changed · +3 lines e533134b9db5
  3. 1mo ago Changed · -516 lines · -3 tokens per session scan C → A 574d34add7aa
  4. 1mo ago Changed · +25 lines b096896ed8ac
  5. 1mo ago Changed · +16 lines scan A → C dfc143514bc9
  6. 1mo ago Changed · +17 lines 99b9e59b3e12
  7. 1mo ago Changed · +18 lines 21468c43acec
  8. 1mo ago Changed · +29 lines 22cbb4047260
  9. 1mo ago Changed · +4 lines 887139de15f6
  10. 1mo ago First seen · 440 lines · 77 tokens per session scan A 7b70de274997

Subscribe to this mod's changes

pi-lens-fixer is an agent published in the GitHub repository apmantza/pi-lens (514 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 562 once invoked, about $0.0003 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-30.

Related

pi-lens-fixer compared with agents from other repositories

pi-lens-fixer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pi-lens-fixerapmantza/pi-lensAgent514yesterdayMITA74Claude Code
component-improverdavila7/claude-code-templatesAgent33kyesterdayMITA39Claude Code
release-validatorrlajous/claude-code-commandsAgent303d agoMITA25Claude Code
FlowSubmitNWatchPRjpoley/flowspecAgent5028d agoApache-2.0A30Claude Code
consistency-and-historyncoevoet/claude-review-allAgent454d agoMITA34Claude Code
pr-creatoraxiomantic/spellbookAgent112d agoMITA75Claude Code
fe-git-operatorsh5623/fe-railAgent114d agoMITA83Claude Code