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.
npx skills add OKHP3/skillz --skill okhp3-replit-repository-janitorgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/okhp3-replit-repository-janitor)<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-replit-repository-janitor"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-replit-repository-janitor/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/okhp3/skillz/okhp3-replit-repository-janitor"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-replit-repository-janitor.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.00151 | $0.02817 |
| Opus 5.5 | $0.00060 | $0.01127 |
| Sonnet 5.5 | $0.00030 | $0.00563 |
| Haiku 4.5 | $0.00015 | $0.00282 |
Grade A, and why
okhp3-replit-repository-janitor 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
89% identical to okhp3-replit-repl-janitor — 38 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.
How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okhp3-replit-repository-janitor
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Safely clean one Replit workspace's Git checkout without confusing generated branch names with proof, a closed pull request with a merged one, or an untidy filename with permission to rename it. The workflow is read-only first, evidence-led, and destructive only after the owner approves exact line items.
Identity migration and evidence
This name replaces okhp3-replit-repl-janitor and its older okhp3-repl-repo-janitor predecessor. The 1.0.1 benchmark is preserved unchanged as historical evidence under its original identity. Version 1.0.2 updates naming and routing; no new live behavioral benchmark is claimed. The repository-local support package remains a separate implementation with additional hosted-lookup safeguards; this migration does not overwrite either variant or claim byte equality between them.
Scope
| In scope | Out of scope |
|---|---|
| One-time cleanup of one Replit checkout | Recurring maintenance; use okhp3-repository-janitor |
| Branch and PR classification against a verified base | Multi-clone reconciliation; use okhp3-repository-janitor |
| Naming and detritus audit | Structural redesign; use okhp3-repository-organizer |
| Exact, owner-approved cleanup execution | Autonomous deletion, merging, renaming, or publishing |
Safety contract
- Start read-only. Run the bundled audit without
--fetch; it reads the current checkout and prints JSON. Fetch separately only when network access is appropriate. Never prune during discovery. - Fail visibly. A missing base ref, failed Git command, detached HEAD, or non-repository path is evidence, not an empty result. Stop and report it.
- Separate three facts. "Merged into
origin/main", "closed pull request", and "abandoned with no PR" are different states. Never substitute one for another. - Names are hints, not verdicts.
subrepl-*,replit-agent, andagent/*suggest generated work but do not prove it is safe to delete. The current branch is never a deletion candidate. - Plan before touching. Return the exact
keep,merge,delete, andreviewbranch buckets plus file actions. Wait for explicit approval of individual destructive lines. - Rename atomically. A file rename must update every importer and link in the same change. A public URL needs a redirect or transition plan.
- Protect recovery paths. Never rewrite
main, force-push, or delete stashes or archive refs under this skill.
What ships with it
7 files 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.
- 1mo ago First seen · 297 lines · 151 tokens per session scan A a47c5f88b009
okhp3-replit-repository-janitor is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed 2d ago), licensed MIT. It adds 151 tokens to every session and 2,817 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to okhp3-replit-repl-janitor, differing in 38 lines, and is treated as a copy.
Other skills, from other repositories
empty-commit
Use when a CI pipeline failed on something unrelated to the code and the PR is blocked — pushes an empty commit to re-trigger CI on the current branch.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
stage
Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
git-commit
A Git assistant for reviewing local changes and creating conventional commit messages, which are standardized summaries of code changes. It can also run Git hooks and push the commit.