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/archive228/loopkit/polishgit clone --depth 1 https://github.com/Archive228/loopkitWhat 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.00037 | $0.00712 |
| Opus 5 | $0.00018 | $0.00356 |
| Sonnet 5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polish — one-shot quality pass over the current diff
Apply six existing quality skills to the changes already in the working tree, in a fixed order, with a single summary at the end. No new features. No behavior changes beyond what each skill authorises.
Scope
This command applies to the CURRENT git diff only. Run git diff first if you're unsure of scope. If the working tree is clean, stop and tell the user there is nothing to polish.
Steps
-
Load the diff:
git diff HEADandgit status --short. Fix on this set of changed files for the whole session; do not wander into untouched code. -
Apply each skill below in order. For each: read the skill file from
skills/<name>/SKILL.md(repo layout) or.claude/skills/<name>/SKILL.md(installed layout), walk its checklist against the diff, and apply the fixes it authorises. If the skill does not apply to this diff (e.g.a11y-passon a backend-only change), recordskippedwith a one-line reason and move on.- simplify — collapse indirection you don't need.
- reduce-nesting — early returns, guard clauses.
- kill-dead-code — prove unreachable, then delete.
- a11y-pass — semantics + keyboard + contrast (UI diffs only).
- loading-empty-error-states — all four states, not just happy path (async views only).
- readme-audit — cold-onboarding check (only if README or public interface changed).
-
Emit exactly ONE summary at the end, as a table:
| skill | action_taken | verdict | |----------------------------|---------------------------------------|-------------------| | simplify | <one line> | applied / skipped | | reduce-nesting | <one line> | applied / skipped | | kill-dead-code | <one line> | applied / skipped | | a11y-pass | <one line> | applied / skipped | | loading-empty-error-states | <one line> | applied / skipped | | readme-audit | <one line> | applied / skipped |
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.
- yesterday First seen · 50 lines · 37 tokens per session scan A 4d1e52e7b3c6
polish is a command published in the GitHub repository Archive228/loopkit (753 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 712 once invoked, about $0.0002 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.