Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Phoenix0531-sudo/tidy-skillnpx agentmods add commands/phoenix0531-sudo/tidy-skill/tidy-doctorWrote 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/commands/phoenix0531-sudo/tidy-skill/tidy-doctor)<a href="https://agentmods.dev/commands/phoenix0531-sudo/tidy-skill/tidy-doctor"><img src="https://agentmods.dev/badge/commands/phoenix0531-sudo/tidy-skill/tidy-doctor/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/commands/phoenix0531-sudo/tidy-skill/tidy-doctor"><img src="https://agentmods.dev/badge/commands/phoenix0531-sudo/tidy-skill/tidy-doctor.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.00000 | $0.00132 |
| Opus 5 | $0.00000 | $0.00066 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
tidy-doctor 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 9d 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
/tidy-doctor
One-shot read-only doctor for skill package presence and repo hygiene.
Command
python scripts/tidy_doctor.py --root . --json
Optional policy / score gate:
python scripts/tidy_doctor.py --root . --policy .tidy-skill.json --min-score 80 --json
Output expectations
- Skill package core files present
- Repo score and rating
- Suspicious root process files (if any)
- Optional score gate vs policy
min_score - Exit
2when hygiene/policy checks fail (CI-friendly)
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.
- 9d ago First seen · 24 lines · 0 tokens per session scan A 157878ba28a3
tidy-doctor is a command published in the GitHub repository Phoenix0531-sudo/tidy-skill (20 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 132 tokens. 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-30.
Other commands, from other repositories
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
map
Generate a dependency map showing how modules and files relate to each other in the codebase.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
find-dead-code
Identify unused code across the codebase.
triage
Triage a bug report (PDF / markdown / text) — extract the issues, prioritize, then run the fix pipeline per issue.
fix
Triage pasted logs/stacks into bugs findings and todos. Does not change application code unless the user confirms.