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/davstr1/peekaboomcp/claude-mdgit clone --depth 1 https://github.com/davstr1/peekabooMCPWrote 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/instructions/davstr1/peekaboomcp/claude-md)<a href="https://agentmods.dev/instructions/davstr1/peekaboomcp/claude-md"><img src="https://agentmods.dev/badge/instructions/davstr1/peekaboomcp/claude-md.svg" alt="Measured on agentmods" 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.01298 | $0.01298 |
| Opus 5 | $0.00649 | $0.00649 |
| Sonnet 5 | $0.00260 | $0.00260 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
peekabooMCP 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 5d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NEVER FUCKING SAY AGAIN "You're absolutely right"
Gigarad Backend - AI Context
Project Overview
Gigarad is a music discovery and radio generation platform that creates personalized radio stations using AI. Users can generate stations based on:
- A seed song (similar to Spotify Radio)
- Text prompts (AI-powered recommendations)
User Commands (prefix with --):
--GCP
Commit and push all staged changes.
--MIND
Before any action, remind yourself:
- This isn’t fucking enterprise. We’re indiehackers, building MVPs—move fast, stay practical.
- DRY (Don’t Repeat Yourself)
- KISS (Keep It Simple, Stupid)
- YAGNI (You Aren’t Gonna Need It)
- SOLID (Single responsibility, Open-closed, Liskov, Interface segregation, Dependency inversion)
- FCP (Favor Composition over Inheritance)
- PoLA (Principle of Least Astonishment)
- SoT (Single Source of Truth)
--WD
Run --X and --MIND.
Do a quick, MVP-level review of the codebase. regarding what's described along with the command.
Write an actionable checklist in /dev-docs/REVIEW-***.md.
Don’t touch code or other docs.
When done, --GCP and output the doc path.
--AP
Run --X and --MIND.
Take the latest review and break it down into a simple, step-by-step action plan with checkboxes—keep splitting steps until atomic.
Save as /docs/ACTION-PLAN-***.md, then --GCP.
--EXE
Run --MIND, then execute the action plan (from file), checking off steps as you go.
Commit and push (--GCP) after each step.
--TERMINATOR
Run --EXE, then --DS.
--CD
Run --MIND.
Find and delete obsolete .md files, then --GCP.
--DS
Don’t stop until the process is totally finished.
--X
Don’t touch the codebase, except for the one file specified (if any).
General Notes
- Reviews and action plans must stay light and MVP-focused—no enterprise BS unless explicitly asked.
- Output file paths for every relevant action.
Tech Stack
- Framework: FastAPI
- Database: PostgreSQL 16 with SQLAlchemy ORM
- Search: Typesense
- Python: 3.13.2
- Server: Uvicorn (dev), Gunicorn (prod)
- Container: Docker with docker-compose
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.
- 5d ago First seen · 163 lines · 1,298 tokens per session scan A 4eee3957b0f5
peekabooMCP CLAUDE.md is an instructions file published in the GitHub repository davstr1/peekabooMCP (0 stars, last pushed 1y ago), licensed MIT. It adds 1,298 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).
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.
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).
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.
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.
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.