Borrowing it
Nothing to install: this file belongs to A/claude-booping. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/A/claude-booping/master/CLAUDE.mdgit clone --depth 1 https://github.com/A/claude-boopingWrote 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/a/claude-booping/claude-md)<a href="https://agentmods.dev/instructions/a/claude-booping/claude-md"><img src="https://agentmods.dev/badge/instructions/a/claude-booping/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.
<a href="https://agentmods.dev/instructions/a/claude-booping/claude-md"><img src="https://agentmods.dev/badge/instructions/a/claude-booping/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.06616 | $0.06616 |
| Opus 5.5 | $0.02646 | $0.02646 |
| Sonnet 5.5 | $0.01323 | $0.01323 |
| Haiku 4.5 | $0.00662 | $0.00662 |
Grade A, and why
claude-booping 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
booping plugin — project guide
Claude Code plugin that grooms and executes plans across user projects. Plans and other run artifacts live in the per-project vault — ~/Claude/{project}/ by default, or a repo-local directory via the .booping marker's vault_path: key. Skills, agents, playbooks, templates, and config live in this repo.
One shipped skill (/playbook); everything procedural is a playbook it drives (groom, develop, code-review, retro, learn, specs, project-manager, setup, migrate, makemigration, playbook-authoring).
Commands
just lint/just typecheck/just pytest— ruff / basedpyright / pytest over both uv projects,booping-python/thenbooping-tracker/.just snapshots— diff committed playbook reports against a fresh hermetic render (writes nothing); a playbook in this repo'svault/_playbooks/joins once it commits a_reports/output.md, rendered against a stub-pinned temp copy of the vault.just snapshots-accept [playbook]— the only writer of the committed reports.just mdcheck— structural rule checks over the rendered reports. Needs themdcheckbinary:cargo install markdown-checker --version 0.1.2 --locked(the crate namedmdcheckis unrelated). It is a user-facing runtime dependency too: groom checks every milestone file with it againstplaybooks/groom/_schemas/milestone.yaml.just e2e [pytest args…]— run both txtar contract corpora through pytest, passing any arguments straight to it (just e2e -k create,just e2e --txtar-update);--txtar-updaterebaselines the selected cases. Cases run in parallel (pytest-xdist,-n auto);--txtar-updateruns serially. A-kexpression that selects in one corpus only leaves the other collecting nothing, which is not a failure.just specs-check—bin/booping specs checkover the core tier,specs/(records shipped to every user), and this repo's project tier, the type directories invault/; needsmdchecktoo.just ci— everything CI runs, in order:lint typecheck pytest snapshots mdcheck specs-check e2e. Run before committing.just eval|smoke|regress <playbook>/<step>(orall) — promptfoo eval suites;just suiteslists them. Runs on subscription auth (claude -p), never in CI; each run posts a sticky, advisory PR comment viascripts/eval-pr-comment.sh(EVAL_PR=0opts out) — no commit status, no merge gate.just docs/just docs-serve— build / preview the public docs site.bin/booping <subcommand> --help— the runtime CLI. Reach for these primitives before adding a command:create <config.path> <dest> --set k=v— writes any config-defined file tree from Jinja templates, filled by--setvars, macros (time, session id, commit) andnext_id(prefix)(the next free numbered name in the destination);--stub-macropins the macros.query— filters, sorts and projects markdown files by frontmatter (--config <spec>or--glob/--where/--columns); the same specs run at render time as the| queryfilter.set <file> k=v— sets, appends (--append) or removes (--remove) frontmatter keys of any file, or keys of the.boopingmarker when the file is one.render/render-playbook— render a template, or a playbook's composed procedure, with full project context.transition <file> <status>/state <file>— move a file along thestates:machine its path matches, hooks included (--playbook/--statenarrow it); report its run's frontier.config <key>— print a merged config value by dotted path.debug-context— dump the assembled context.session-stats— mine active minutes, tokens and models from artefacts' stamped sessions.status— the project status computed from the vault, short or per-section detail.run(groom,develop,code-review,ack) — launch a recorded headless run, ack a finished one.plan(split) — cut a one-file draft into milestone files; check milestones against the contract.specs(ls,next,check,scan,init,site,site-index) — list, number, check and publish typed spec records of a tier;scanfiles an open item per mark and check finding.
bin/booping-tracker <verb> --help— the task-tracker CLI:states,show,comment,issue-create,issue-update,relate,sync. Reference: booping-tracker/README.md.
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.
- today Changed · +26 lines · +2,434 tokens per session b86dc2f7421f
- 1mo ago Changed · +7 lines · +883 tokens per session bae02e9c0623
- 1mo ago First seen · 90 lines · 3,299 tokens per session scan A 183a6cffc793
claude-booping CLAUDE.md is an instructions file published in the GitHub repository A/claude-booping (14 stars, last pushed yesterday), licensed MIT. It adds 6,616 tokens to every session, about $0.0265 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.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.