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.
git clone --depth 1 https://github.com/yzhao062/anywhere-agentsWrote 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/yzhao062/anywhere-agents/readme-polish)<a href="https://agentmods.dev/commands/yzhao062/anywhere-agents/readme-polish"><img src="https://agentmods.dev/badge/commands/yzhao062/anywhere-agents/readme-polish/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/yzhao062/anywhere-agents/readme-polish"><img src="https://agentmods.dev/badge/commands/yzhao062/anywhere-agents/readme-polish.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.00079 |
| Opus 5 | $0.00000 | $0.00039 |
| Sonnet 5 | $0.00000 | $0.00016 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
readme-polish 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
Read and follow the skill definition. Look for it at skills/readme-polish/SKILL.md first, then .claude/skills/readme-polish/SKILL.md, then .agent-config/repo/skills/readme-polish/SKILL.md.
Apply it to the user's current task. Also read the supporting files under the skill's references/ directory as needed.
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 · 4 lines · 0 tokens per session scan A d9bc173c4b69
readme-polish is a command published in the GitHub repository yzhao062/anywhere-agents (244 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 79 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
diagnose-deeptrace
Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device.
troubleshoot-experience
Troubleshoot a user's digital experience using ZDX scores, metrics, and network path data.
troubleshoot-user
Cross-product troubleshooting of user connectivity across ZCC, ZDX, ZPA, and ZIA.
audit-ssl
Audit ZIA SSL inspection rules -- list rules by action (INSPECT, DONOTINSPECT, DONOTDECRYPT, BLOCK), identify bypasses, and assess risk.
investigate-sandbox
Investigate ZIA Sandbox file analysis -- check sandbox reports, quota, SSL prerequisite, and diagnose file block/quarantine issues.
create-access-rule
Create a ZPA access policy rule with v2 conditions for application access control.