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-repl-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-repl-janitor)<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-replit-repl-janitor"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-replit-repl-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-repl-janitor"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-replit-repl-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.02633 |
| Opus 5 | $0.00076 | $0.01316 |
| Sonnet 5 | $0.00030 | $0.00527 |
| Haiku 4.5 | $0.00015 | $0.00263 |
Grade A, and why
okhp3-replit-repl-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 yesterday.
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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okhp3-replit-repl-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.
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.
- yesterday Changed · +17 lines d69790b01dc2
- 5d ago First seen · 266 lines · 151 tokens per session scan A d3477c5589fa
okhp3-replit-repl-janitor is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 151 tokens to every session and 2,633 once invoked, about $0.0008 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-09-05.
Other skills, from other repositories
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
pm-release
A release-planning workflow for preparing software to go live, including checks, deployment choices, timing, and rollback conditions.
swe-workflow
Orchestrates the full five-stage flow from raw idea to shipped PR — grill-with-docs → to-prd → to-issues → triage → worktree+planning-with-files. Each stage answers one question (What do I want? / What does done look like? / What are the units of work? / What's actionable? / Build it). Use when the user has an idea…
private-fork-sync
Make a public GitHub fork private and keep it synced with its upstream parent. Use when the user wants to make a fork private, or to pull/sync newer commits from the upstream parent into their fork.
skill-repository-maintainer
A maintenance guide for checking, auditing, and synchronising a Codex Skill repository. It covers package structure, metadata, release boundaries, and differences between the source and installed folders.
git-worktree
Use this skill whenever a task involves running parallel work on a git repository without conflicts — e.g. "fix this bug while I keep working on my feature", "run Claude on two branches at once", "work on this task in isolation", "create a throwaway branch for this experiment", or anything where two agents or sessions…