Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/afaizalam2003/Master-claude-skillWrote 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/afaizalam2003/master-claude-skill/clean)<a href="https://agentmods.dev/commands/afaizalam2003/master-claude-skill/clean"><img src="https://agentmods.dev/badge/commands/afaizalam2003/master-claude-skill/clean/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/afaizalam2003/master-claude-skill/clean"><img src="https://agentmods.dev/badge/commands/afaizalam2003/master-claude-skill/clean.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.00019 | $0.00390 |
| Opus 5.5 | $0.00008 | $0.00156 |
| Sonnet 5.5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
clean 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.
This is a copy
100% identical to clean — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Clean up stale branches that have been merged or are no longer needed.
Steps
- List local branches to delete (excluding
main,dev,gh-pages):
git branch | grep -v -E '^\*|main$|dev$|gh-pages$'
Report what will be deleted. If no branches found, say "No local branches to clean" and skip to step 3.
- Delete local branches that are fully merged:
git branch -d <branch-name>
If a branch is not fully merged, report it to the user and ask whether to force-delete. Do NOT force-delete without confirmation.
- List remote branches to delete (excluding
main,dev,gh-pages,HEAD):
git branch -r | grep -v -E 'origin/main$|origin/dev$|origin/gh-pages$|origin/HEAD'
Report what will be deleted. If no branches found, say "No remote branches to clean" and skip to step 5.
- Confirm with the user before deleting remote branches. Show the full list and wait for approval. Then delete:
git push origin --delete <branch-names>
- Prune stale remote refs:
git remote prune origin
- Report final state:
git branch # local
git branch -r # remote
Present a summary:
| Item | Count |
|---|---|
| Local branches deleted | N |
| Remote branches deleted | N |
| Remaining local | main, dev |
| Remaining remote | origin/main, origin/dev, origin/gh-pages |
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 · 60 lines · 19 tokens per session scan A 03ed9e5e4f25
clean is a command published in the GitHub repository afaizalam2003/Master-claude-skill (2 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 390 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to clean, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
commit
A command that checks staged Git changes and creates a commit from them.