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 agentmods add agents/atharva-again/samvaad/janitorgit clone --depth 1 https://github.com/atharva-again/samvaadWrote 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/atharva-again/samvaad/janitor)<a href="https://agentmods.dev/agents/atharva-again/samvaad/janitor"><img src="https://agentmods.dev/badge/agents/atharva-again/samvaad/janitor.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00667 |
| Opus 5 | $0.00010 | $0.00333 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
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 3d 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
88% identical to Janitor — 6 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 — 90 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.
- 3d ago First seen · 90 lines · 19 tokens per session scan A d0985821496c
janitor is an agent published in the GitHub repository atharva-again/samvaad (2 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 667 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to Janitor, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.