Borrowing it
Nothing to install: this file belongs to xiaolai/vmark. 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/xiaolai/vmark/main/.claude/commands/repo-clean-up.mdgit clone --depth 1 https://github.com/xiaolai/vmarkWrote 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/commands/xiaolai/vmark/repo-clean-up)<a href="https://agentmods.dev/commands/xiaolai/vmark/repo-clean-up"><img src="https://agentmods.dev/badge/commands/xiaolai/vmark/repo-clean-up/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/commands/xiaolai/vmark/repo-clean-up"><img src="https://agentmods.dev/badge/commands/xiaolai/vmark/repo-clean-up.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.00012 | $0.00294 |
| Opus 5.5 | $0.00005 | $0.00118 |
| Sonnet 5.5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
repo-clean-up 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 2mo 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.
What it actually says
Repository Cleanup
Clean up the remote repository by removing failed CI artifacts and stale branches.
Step 1: Delete Failed GitHub Actions Runs
gh run list --status failure --limit 100 --json databaseId --jq '.[].databaseId'
Delete each run with gh run delete <id>.
Report: Deleted N failed runs.
Step 2: Delete Canceled GitHub Actions Runs
gh run list --status cancelled --limit 100 --json databaseId --jq '.[].databaseId'
Delete each run with gh run delete <id>.
Report: Deleted N canceled runs.
Step 3: Delete Stale Remote Branches
List all remote branches except main:
git fetch --prune
gh api repos/{owner}/{repo}/branches --paginate --jq '.[].name' | grep -v '^main$'
Delete each branch with gh api -X DELETE repos/{owner}/{repo}/git/refs/heads/{branch}.
Report: Deleted N remote branches.
Step 4: Prune Local Tracking References
git fetch --prune
Summary
Report total cleanup: Cleanup complete: N failed runs, N canceled runs, N branches removed.
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.
- 2mo ago First seen · 51 lines · 12 tokens per session scan A 21192ad0d719
repo-clean-up is a command published in the GitHub repository xiaolai/vmark (878 stars, last pushed yesterday), licensed ISC. It adds 12 tokens to every session and 294 once invoked, about $0.0000 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 commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
issue-to-mr-setup
Create an automation that implements GitLab issues when a configurable trigger label is applied. Polls one or more projects deterministically, clones the default branch, starts one OpenHands conversation per label event, then commits, pushes, and opens the merge request itself.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
ship
Deploy feature through automated staging validation to production with rollback testing.
run-plan
Execute implementation plan phases for a change.
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.