Borrowing it
Nothing to install: this file belongs to webhook-co/webhook. 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/webhook-co/webhook/main/.cursor/commands/clean-gone.mdgit clone --depth 1 https://github.com/webhook-co/webhookWrote 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/webhook-co/webhook/clean-gone)<a href="https://agentmods.dev/commands/webhook-co/webhook/clean-gone"><img src="https://agentmods.dev/badge/commands/webhook-co/webhook/clean-gone/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/webhook-co/webhook/clean-gone"><img src="https://agentmods.dev/badge/commands/webhook-co/webhook/clean-gone.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.00000 | $0.00248 |
| Opus 5.5 | $0.00000 | $0.00099 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
clean-gone 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 1mo 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
/clean-gone
Prune local branches whose remote tracking branch has been deleted (typically after their PR merged).
How to run
- Update remote state and prune stale remote-tracking refs:
git fetch --prune. - Find local branches marked
[gone]:git branch -vvand select the ones whose upstream shows: gone]. - Show me the candidate list before deleting anything. Never delete the current branch or the
default branch (
main/master). - Delete the confirmed branches with
git branch -d(safe delete — only fully-merged branches). If one isn't merged,-dwill refuse: report it and let me decide; do not silently-D(force-delete) a branch that may carry unmerged work.
Hard rules
- Local-only operation: never touch the remote, never delete remote branches, never force-push.
- Don't
-Dforce-delete unless I explicitly confirm that branch — losing unmerged commits is not an acceptable way to "clean up." - Leave
main/masterand the current branch alone.
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.
- 1mo ago First seen · 22 lines · 0 tokens per session scan A bbf8eacef1c5
clean-gone is a command published in the GitHub repository webhook-co/webhook (0 stars, last pushed 18d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 248 tokens. 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 commands, from other repositories
release
A typical CI release creates the release, associates commits, finalizes it, and records a deploy. The sentry release create examples above show the full sequence.
repo
Agentic tooling for Sentry.
replay
You are reconstructing the historical evolution of this sprint by recompiling every version of claims.json from git history.
post-release.en
Read and execute the post-release skill from .agents/skills/post-release/SKILL.md.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
afsr
Review feature spec - improve the spec itself before implementation (shortcut for feature-spec-review).