Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TweekFawkes/promptsnpx agentmods add skills/tweekfawkes/prompts/gitcleanWrote 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/skills/tweekfawkes/prompts/gitclean)<a href="https://agentmods.dev/skills/tweekfawkes/prompts/gitclean"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/gitclean/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/skills/tweekfawkes/prompts/gitclean"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/gitclean.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.00118 | $0.01255 |
| Opus 5.5 | $0.00047 | $0.00502 |
| Sonnet 5.5 | $0.00024 | $0.00251 |
| Haiku 4.5 | $0.00012 | $0.00126 |
Grade A, and why
gitclean 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gitclean
Use this skill only for a finished task branch that should be merged into the repository's main branch and then retired. The goal is to leave main current, preserve a visible retired worktree under delete_me, and reduce confusion for other local agents. For worktrees created by gitready, the default retirement path is a sibling delete_me/ directory next to the worktree.
Required Checks
-
Read the repo's
CLAUDE.md(orAGENTS.md) and follow its Git, verification, and cleanup rules. -
Identify the current worktree, current branch, main branch, and all local worktrees:
git rev-parse --show-toplevel git branch --show-current git worktree list --porcelain git status --short -
Stop if the current branch is
main,master, or detached. This skill retires feature worktrees only. -
Stop if this worktree or the main worktree is dirty. Review, stage, and commit intentional task changes first; never sweep unrelated files into a cleanup commit.
-
Run the repo's required verification before merging — for example:
bash scripts/smoke.sh # or the repo's test suite / lint / buildIf that is impossible, run the strongest relevant test/lint/build checks and state exactly what could not run.
Preferred Automation
Use the bundled helper after the required checks pass:
bash .claude/skills/gitclean/scripts/gitclean.sh \
--repo "$(pwd)" \
--verified "bash scripts/smoke.sh"
Useful options:
--dry-run: print the planned merge and retirement steps without changing files.--main <branch>: use a non-default main branch.--no-push: merge locally but do not push main.--verified <text>: record the verification command(s) that passed before cleanup.--keep-branch: keep the local task branch after detaching the retired worktree.--delete-remote-branch: delete the remote task branch after main is pushed. Use only when the user asked for remote branch cleanup or the repo clearly expects it.--target-parent <path>: place the retired worktree under a specificdelete_meparent.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 130 lines · 118 tokens per session scan A 20e96a2ed9f2
gitclean is a skill published in the GitHub repository TweekFawkes/prompts (2 stars, last pushed 1mo ago), licensed Unlicense. It adds 118 tokens to every session and 1,255 once invoked, about $0.0005 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-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.