Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Sassy-Dog/sassydog-skills/plugin install sassy-dogWrote 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/sassy-dog/sassydog-skills/repo-cleanup)<a href="https://agentmods.dev/skills/sassy-dog/sassydog-skills/repo-cleanup"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/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.
<a href="https://agentmods.dev/skills/sassy-dog/sassydog-skills/repo-cleanup"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/repo-cleanup.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.00210 | $0.05714 |
| Opus 5 | $0.00105 | $0.02857 |
| Sonnet 5 | $0.00042 | $0.01143 |
| Haiku 4.5 | $0.00021 | $0.00571 |
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 11d 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Cleanup
The shared mechanics behind a repo's tidy-repo. A generated tidy-repo is thin: it holds project
facts and delegates the actual reconciliation here, so the tricky git plumbing (the [gone] grep
trap, squash-merge -D, stash triage by PR linkage) lives in exactly one place.
This skill does not own the top-level cleanup request — the per-repo generated tidy-repo does,
and calls this skill by name. It also pairs with the read-only sassy-dog:repo-health (health
= read scan; cleanup = write reconcile) and with the built-in commit-commands:clean_gone (a
narrower [gone]-only sweep — this skill supersedes it with stash/untracked/label handling).
Inputs to establish first
The caller (a generated tidy-repo, or the user directly) supplies these. Resolve any that are
missing before acting:
- Repo —
owner/name. If not given, resolve dynamically (don't hardcode):REPO=$(gh repo view --json nameWithOwner --jq .nameWithOwner). - Default branch — defaults to
main. Used as the reconcile target and the "never delete" guard. - Dep/version-file globs — files whose presence in a stash blocks small-content auto-drop
(e.g.
package.json,bun.lock,pubspec.yaml,*.csproj, migration dirs). Stack-specific. - Noise allowlist — extra auto-discard patterns beyond the universal defaults (build/output
dirs like
**/node_modules/,**/.dart_tool/,**/build/). - Never-discard list — gitignored-but-precious files to leave untouched (e.g.
.env.local). delete_branch_on_merge— whether GitHub auto-deletes the head branch on merge (makes step 7 normally a no-op). Read from repo settings if unknown.- Claim label (optional) — a take-it-style in-progress label (e.g.
status:in-progress) to clear on issues whose work already merged. Omit if the repo has no claim-label convention.
Acting principle (steps 3–4 and 8): ASSESS first, act on what you're confident about, escalate
only on mixed signal — substantive WIP, dep-file touches, abandoned-but-non-trivial work. Asking on
every .DS_Store defeats the purpose; never confirming on a 600-line orphan stash loses real work.
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.
- 11d ago First seen · 394 lines · 210 tokens per session scan A 07174f2ac66e
repo-cleanup is a skill published in the GitHub repository Sassy-Dog/sassydog-skills (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 210 tokens to every session and 5,714 once invoked, about $0.0011 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-08-31.
Other skills, from other repositories
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
resolving-merge-conflicts
Use when a git merge or rebase reports conflicts and the operation is in progress.