Borrowing it
Nothing to install: this file belongs to moollaza/repo-remover. 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/moollaza/repo-remover/main/CLAUDE.mdgit clone --depth 1 https://github.com/moollaza/repo-removerWrote 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/moollaza/repo-remover/claude-md)<a href="https://agentmods.dev/instructions/moollaza/repo-remover/claude-md"><img src="https://agentmods.dev/badge/instructions/moollaza/repo-remover/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/moollaza/repo-remover/claude-md"><img src="https://agentmods.dev/badge/instructions/moollaza/repo-remover/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.01537 | $0.01537 |
| Opus 5 | $0.00768 | $0.00768 |
| Sonnet 5 | $0.00307 | $0.00307 |
| Haiku 4.5 | $0.00154 | $0.00154 |
Grade A, and why
repo-remover 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 12d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Remover
GitHub repository management tool — bulk view, archive, and delete repos. Zero-knowledge, client-side only.
Stack
Vite 8, React 18, React Router 7, TypeScript 5.9, Tailwind CSS 4, Vitest + RTL + Playwright, MSW, Octokit (GraphQL + REST), SWR, Sentry + Fathom, bun
Deployed on Cloudflare Workers (not Vercel).
Constraints
- Zero-knowledge architecture: all GitHub API calls client-side only, no backend
- PAT-based auth: only viable client-side GitHub auth option (no OAuth, no PKCE)
- No user data, tokens, or PII sent to any server
- Tailwind CSS only: no component library — use plain Tailwind + CSS custom properties for theming
- bun as package manager (not npm)
Commands
bun run dev # dev server (localhost:5173)
bun run build # tsc + vite production build
bun run lint # eslint
bun run lint:fix # eslint with auto-fix
bun run test:unit # unit tests (vitest)
bun run test:e2e # playwright E2E tests
bun run test:e2e:fast # E2E with fast-fail
bun run test:all # unit + E2E
npx tsc --noEmit # typecheck (must pass before merge)
Before every commit: bun run lint && bun run test:unit && bun run build
Commits
Use Conventional Commits — release-please uses these to auto-generate changelogs and determine semver bumps.
fix: ...→ patch (2.0.1)feat: ...→ minor (2.1.0)feat!: ...orBREAKING CHANGE:footer → major (3.0.0)chore:,docs:,refactor:,test:,ci:→ no release
Workflow
Uses Compound Engineering workflow: Plan → Work → Review → Compound.
/lfg— full autonomous pipeline (plan → work → review → compound)/slfg— same but with swarm parallelism for work + review/ce-plan— structured planning only/ce-work— execute a plan/ce-review— multi-agent code review/ce-compound— document learnings indocs/solutions/
Plans go in docs/plans/. Solutions go in docs/solutions/.
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.
- 12d ago First seen · 114 lines · 1,537 tokens per session scan A 06d845b7dcbd
repo-remover CLAUDE.md is an instructions file published in the GitHub repository moollaza/repo-remover (391 stars, last pushed 11d ago), licensed MIT. It adds 1,537 tokens to every session, about $0.0077 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.
Other instructions, from other repositories
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.
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 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).
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).