vibepulse: Command for Claude Code

.claude/commands/repo-cleanup.md

repo-cleanup is a command for Claude Code from niclasvestlund-YT/vibepulse. It costs 36 tokens per session (2,010 once invoked), scanned A, original, MIT.

A repository-cleanup procedure that finds likely unused files and reports evidence before anything is removed. A repository is the project folder containing its code and related files.

In plain words
What is it for?
Finding regenerable build files, obsolete documents, orphaned assets, and other cleanup candidates, then proposing their removal for approval.
Why use it?
It separates investigation from deletion, reducing the risk of removing files that the project still needs.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is niclasvestlund-YT/vibepulse's own configuration. It tells Claude Code how to work on vibepulse 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 vibepulse configures →

Reuse

Borrowing it

Nothing to install: this file belongs to niclasvestlund-YT/vibepulse. 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/niclasvestlund-YT/vibepulse/main/.claude/commands/repo-cleanup.md
Clone the repo
git clone --depth 1 https://github.com/niclasvestlund-YT/vibepulse

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 repo-cleanup

README.md
[![agentmods](https://agentmods.dev/badge/commands/niclasvestlund-yt/vibepulse/repo-cleanup/github.svg)](https://agentmods.dev/commands/niclasvestlund-yt/vibepulse/repo-cleanup)
Your own site
<a href="https://agentmods.dev/commands/niclasvestlund-yt/vibepulse/repo-cleanup"><img src="https://agentmods.dev/badge/commands/niclasvestlund-yt/vibepulse/repo-cleanup/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 repo-cleanup

Your own site · 80×15
<a href="https://agentmods.dev/commands/niclasvestlund-yt/vibepulse/repo-cleanup"><img src="https://agentmods.dev/badge/commands/niclasvestlund-yt/vibepulse/repo-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,010 The whole file, excluding the scripts and references it only reads on demand.
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.00036 $0.02010
Opus 5 $0.00018 $0.01005
Sonnet 5 $0.00007 $0.00402
Haiku 4.5 $0.00004 $0.00201

Measured 5d ago against content hash b5adfd0fe5b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

repo-cleanup 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.

.claude/commands/repo-cleanup.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repo cleanup — inventera först, radera sedan

Scope: $ARGUMENTS (tomt = hela repot).

Städning är två jobb med motsatt riskprofil: att hitta kandidater är billigt och ofarligt, att ta bort dem är inte det. Gör dem i den ordningen och blanda dem aldrig. Det här körningen producerar en rapport. Du raderar ingenting förrän jag har godkänt specifika rader i den.

Läs CLAUDE.md, AGENTS.md och README.md innan du börjar — de säger vad som är bärande i det här repot.

Fas 1 — inventering (den här körningen)

Arbeta kategori för kategori. Varje kandidat får en rad med bevis, aldrig ett intryck. "Ser oanvänd ut" är inte ett bevis.

De sex kategorierna

  1. Regenerbara artefakter som ligger spårade — byggutdata, cacher, lockfiler för verktyg ingen kör, vendrade kopior som ett hämtskript redan producerar. Bevis: kommandot som återskapar filen.
  2. Överspelade engångsdokument — utredningsanteckningar, körscheman för en session, brainstorms vars slutsats sedan landat i ett permanent dokument eller i koden. Bevis: var slutsatsen bor nu.
  3. Föräldralösa assets — bilder, fixtures, fonter, exempelpayloads som inget refererar. Bevis: sökningen som kommer tillbaka tom — sök på innehåll, inte bara filnamn: assets refereras via glob, via katalog och från genererade filer.
  4. Död kod — symbol, fil eller modul utan anropare och utan byggpost. Bevis: både grep-resultatet och frånvaron i CMake/Kconfig/__init__/exports.
  5. Dubblering — samma sak sagd i tre dokument, samma hjälpfunktion skriven två gånger. Bevis: båda platserna, och vilken du föreslår att behålla.
  6. Rutten konfiguration — ignore-regler för sökvägar som inte finns, CI-steg för jobb som togs bort, beroenden inget importerar.

Aldrig kandidater

Rör inte dessa, oavsett hur oanvända de ser ut:

  • LICENSE, SECURITY.md, CONTRIBUTING.md, CHANGELOG.md, docs/releases/
  • secrets.h.example — mallen ÄR dokumentationen av konfigurationsytan
  • spec/ — hårdvarusanningen; docs/lessons.md — varje post är ett ärr
  • third_party/, dependencies.lock, partitions.csv, sdkconfig.defaults
  • platform/fonts/*.c — genererade men committade med flit (bygget ska varken behöva node eller nät)
  • Allt som .gitignore täcker och som inte är spårat. En fil slutar inte vara spårad för att en ignore-regel tillkommer efteråt — den ligger kvar i repot och är då en giltig kandidat i kategori 1. Fråga git ls-files, inte git check-ignore
  • Git-historik. Ingen filter-branch, ingen BFG, ingen force-push.

Read the full file on GitHub · 129 lines

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. 5d ago First seen · 129 lines · 36 tokens per session scan A b5adfd0fe5b0

Subscribe to this mod's changes

repo-cleanup is a command published in the GitHub repository niclasvestlund-YT/vibepulse (194 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 2,010 once invoked, about $0.0002 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-09-07.