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 agentmods add instructions/mantisware/peepit/claude-mdgit clone --depth 1 https://github.com/MantisWare/peepitWhat 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 | $0.01296 | $0.01296 |
| Opus 5 | $0.00648 | $0.00648 |
| Sonnet 5 | $0.00259 | $0.00259 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
peepit 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 2d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
To test this project interactive we can use:
PEEPIT_AI_PROVIDERS="ollama/llava:latest" npx @modelcontextprotocol/inspector npx -y @mantisware/peepit-mcp@beta
Common Commands
Building
# Build TypeScript server
npm run build
# Build Swift CLI only
npm run build:swift
# Build everything (Swift CLI + TypeScript)
npm run build:all
# Build universal Swift binary with optimizations
./scripts/build-swift-universal.sh
Testing
# Run all tests
npm test
# Run tests with coverage
npm run test:coverage
# Run tests in watch mode
npm run test:watch
# Run Swift tests (CI-compatible tests only)
npm run test:swift
# Run Swift tests with local-only tests (requires test host app)
cd peepit-cli
RUN_LOCAL_TESTS=true swift test
# Full integration test suite
npm run test:integration
Local Testing with Test Host App
For comprehensive testing including actual screenshot functionality:
-
Open the test host app:
cd peepit-cli/TestHost swift run -
The test host app provides:
- Real-time permission status (Screen Recording, Accessibility, CLI availability)
- Interactive permission prompts
- Test pattern windows for screenshot validation
- Log output for debugging
-
Run local-only tests with the test host running:
cd peepit-cli RUN_LOCAL_TESTS=true swift test --filter LocalIntegration -
Or use Xcode for better debugging:
- Open
Package.swiftin Xcode - Run the test host app target first
- Run tests with local environment variable:
RUN_LOCAL_TESTS=true
- Open
Note: Local tests require actual system permissions and are designed to work with the test host application for controlled testing scenarios.
Development
# Start TypeScript compilation in watch mode
npm run dev
# Run the server directly
npm start
# Clean build artifacts
npm run clean
# Lint Swift code
npm run lint:swift
# Format Swift code
npm run format:swift
# Prepare for release (comprehensive checks)
npm run prepare-release
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.
- 2d ago First seen · 172 lines · 1,296 tokens per session scan A 51f779d41138
peepit CLAUDE.md is an instructions file published in the GitHub repository MantisWare/peepit (2 stars, last pushed 1y ago), licensed MIT. It adds 1,296 tokens to every session, about $0.0065 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-31.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.