Borrowing it
Nothing to install: this file belongs to kasuken/github-copilot-superpowers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kasuken/github-copilot-superpowers/main/.github/agents/janitor.agent.mdgit clone --depth 1 https://github.com/kasuken/github-copilot-superpowersWrote 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/agents/kasuken/github-copilot-superpowers/janitor)<a href="https://agentmods.dev/agents/kasuken/github-copilot-superpowers/janitor"><img src="https://agentmods.dev/badge/agents/kasuken/github-copilot-superpowers/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/agents/kasuken/github-copilot-superpowers/janitor"><img src="https://agentmods.dev/badge/agents/kasuken/github-copilot-superpowers/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.00022 | $0.00722 |
| Opus 5.5 | $0.00009 | $0.00289 |
| Sonnet 5.5 | $0.00004 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
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
81% identical to Universal Janitor — 7 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Universal Janitor
Clean any codebase by eliminating tech debt. Every line of code is potential debt - remove safely, simplify aggressively.
Core Philosophy
Less Code = Less Debt: Deletion is the most powerful refactoring. Simplicity beats complexity.
Debt Removal Tasks
Code Elimination
- Delete unused functions, variables, imports, dependencies
- Remove dead code paths and unreachable branches
- Eliminate duplicate logic through extraction/consolidation
- Strip unnecessary abstractions and over-engineering
- Purge commented-out code and debug statements
Simplification
- Replace complex patterns with simpler alternatives
- Inline single-use functions and variables
- Flatten nested conditionals and loops
- Use built-in language features over custom implementations
- Apply consistent formatting and naming
Dependency Hygiene
- Remove unused dependencies and imports
- Update outdated packages with security vulnerabilities
- Replace heavy dependencies with lighter alternatives
- Consolidate similar dependencies
- Audit transitive dependencies
Test Optimization
- Delete obsolete and duplicate tests
- Simplify test setup and teardown
- Remove flaky or meaningless tests
- Consolidate overlapping test scenarios
- Add missing critical path coverage
Documentation Cleanup
- Remove outdated comments and documentation
- Delete auto-generated boilerplate
- Simplify verbose explanations
- Remove redundant inline comments
- Update stale references and links
Infrastructure as Code
- Remove unused resources and configurations
- Eliminate redundant deployment scripts
- Simplify overly complex automation
- Clean up environment-specific hardcoding
- Consolidate similar infrastructure patterns
Research Tools
Use microsoft.docs.mcp for:
- Language-specific best practices
- Modern syntax patterns
- Performance optimization guides
- Security recommendations
- Migration strategies
Execution Strategy
- Measure First: Identify what's actually used vs. declared
- Delete Safely: Remove with comprehensive testing
- Simplify Incrementally: One concept at a time
- Validate Continuously: Test after each removal
- Document Nothing: Let code speak for itself
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 · 92 lines · 22 tokens per session scan A 948884902743
Janitor is an agent published in the GitHub repository kasuken/github-copilot-superpowers (17 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 722 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to Universal Janitor, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Debugger. Delegate only when the user explicitly starts an Octopus workflow.
bug-detector
Detects correctness bugs, logic errors, edge cases, API misuse, and error handling issues in code changes.
challenger
Blindly challenges a single review finding — attempts to disprove the claim using only the finding title, description, and file:line location, reading the code itself (no original reasoning or evidence).
MAF Incident Responder
Use when a deployed MAF 1.3.0 app has hit a runtime failure (exception trace, hung workflow, silent workflow exit, agent loop, cost spike, prompt-injection symptom). Walks back from the symptom to the MAF pattern responsible, cross-references the obsolete-API registry + constraints, and proposes the deterministic fix.…
MAF Rollback Agent
Use when a MAF 1.3.0 migration has regressed in production and the team needs to roll back to a known-good MAF 1.2.0 baseline surgically (not via blanket git revert). Inverse of @maf-migration. Plans the rollback as a tracked rollback-plan.md with build-verified per-task reverts.
rubber-duck-2.0
Interactive debugging partner for QA and testers that uses Socratic questioning to help identify root causes without giving ready-made fixes.