agentmods.dev

pi-lens: Instructions file for Claude Code

CLAUDE.md

pi-lens CLAUDE.md is an instructions file for Claude Code from apmantza/pi-lens. It costs 491 tokens per session, scanned A, original, MIT.

Project instructions for AI assistants working on the pi-lens codebase. They define required build, testing, version-control, changelog, and pull-request practices.

In plain words
What is it for?
Building before tests, proving regression tests fail before a fix, updating changelog fragments, running the right test scope, and checking that pushed pull requests actually run tests and linting.
Why use it?
They prevent common mistakes such as testing outdated compiled code, hiding changes with git stash, or creating incomplete pull requests.

Instructions file for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions AGENTS.md.

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 →

not rated 399repo +18 changed today A scan 491 tokens original MIT
View source ↗ apmantza/pi-lens
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.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 CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/apmantza/pi-lens/claude-md"><img src="https://agentmods.dev/badge/instructions/apmantza/pi-lens/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 491 This file is loaded in full into every session.
When invoked 491 The same file — it is already loaded in full.
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.00491 $0.00491
Opus 5 $0.00246 $0.00246
Sonnet 5 $0.00098 $0.00098
Haiku 4.5 $0.00049 $0.00049

Measured today against content hash 42c2483abbda, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pi-lens CLAUDE.md 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 today.

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.md · 37 lines

What it actually says

CLAUDE.md

Deliberately thin. The canonical engineering contract for this repo lives in AGENTS.md — read it before writing code, especially "Recurring defect shapes — screen against these BEFORE you write code".

Non-negotiables (the short list)

  • npm run build before any test run. Compiled clients/*.js are the runtime; unbuilt TypeScript changes are silently ignored by the tests.
  • git stash is forbidden — it is repo-global across worktrees. Use git diff > fix.patch / git checkout -- / git apply. Mechanically enforced (with three sibling rules) by the scripts/hooks/guard-bash.mjs PreToolUse hook (#2699) — see AGENTS.md "Contributing".
  • Prove every new regression test red on pre-fix code, and keep the output.
  • Run targeted test files while iterating. The full suite runs once, and is serialized machine-wide (#1112); CI is authoritative.
  • Changelog: one fragment file in .changelog/ per change. Never hand-edit CHANGELOG.md.
  • PRs: issue ref in the title. closes only when every acceptance criterion is met; otherwise refs plus an issue comment naming the remainder. After any push, verify Unit tests and Lint actually execute on the new head — a merge-conflicted (DIRTY) PR silently skips them.
  • Availability/probe code: apply the recurring-defect catalog in AGENTS.md, especially shapes 10, 13, 17, and 18. Repeated degradations use recordDegradationOnce / incrementDegradationCount.

Orchestration assets

  • .claude/agents/pi-lens-fixer.md — role playbook for implementing a fix from an issue spec.
  • .claude/agents/pi-lens-reviewer.md — role playbook for adversarial pre-merge review.
  • .claude/agents/pi-lens-investigator.md — role playbook for log forensics and root-causing runtime behavior.
  • .claude/skills/merge-train/SKILL.md — the review → verify → merge policy.
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. today Changed · +2 lines · +43 tokens per session 42c2483abbda
  2. 9d ago First seen · 35 lines · 448 tokens per session scan A d874c105e395

Subscribe to this mod's changes

pi-lens CLAUDE.md is an instructions file published in the GitHub repository apmantza/pi-lens (399 stars, last pushed today), licensed MIT. It adds 491 tokens to every session, about $0.0025 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens