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 commands/arshiaecho/janitor/janitor-devicegit clone --depth 1 https://github.com/ArshiaEcho/janitorWhat 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.00026 | $0.00109 |
| Opus 5 | $0.00013 | $0.00055 |
| Sonnet 5 | $0.00005 | $0.00022 |
| Haiku 4.5 | $0.00003 | $0.00011 |
Grade A, and why
janitor-device 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 2d 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.
What it actually says
Load and run the janitor-device skill on the current machine. Detect the OS first, then walk the full five-phase workflow: diagnose → identify villains → present findings and ask for permission → fix (with copy-paste admin blocks for anything elevated) → verify with a before/after table and close with a custom analogy. Every mutation requires explicit user confirmation. Everything is reversible.
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.
- 2d ago First seen · 7 lines · 26 tokens per session scan A c7a4271a4bb8
janitor-device is a command published in the GitHub repository ArshiaEcho/janitor (6 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 109 once invoked, about $0.0001 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 commands, from other repositories
app
Control macOS apps via peekaboo app.
mcp
Run Peekaboo as an MCP server via peekaboo mcp.
drag
Execute drag-and-drop flows via peekaboo drag.
move
Position the cursor via peekaboo move.
set-value
Set accessibility element values directly via peekaboo set-value.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.