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/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/polish-sweep)<a href="https://agentmods.dev/commands/technickai/ai-coding-config/polish-sweep"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/polish-sweep/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/technickai/ai-coding-config/polish-sweep"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/polish-sweep.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.00023 | $0.00911 |
| Opus 5.5 | $0.00009 | $0.00364 |
| Sonnet 5.5 | $0.00005 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
polish-sweep 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polish-sweep
$ARGUMENTS
This is the "last 15%" - issues that users feel but can't articulate. Missing feedback, inconsistent behaviors, dead-end errors, and code patterns that lead to UX problems.
Focus on HIGH and MEDIUM severity findings. Low severity is polish-on-polish - nice to have but not blocking.
- No argument or "all": Scan
components/andapp/directories - "components": Scan only
components/directory - "app": Scan only
app/directory - Specific path: Scan the provided directory
Note: Default directories are optimized for Next.js/React projects. For other frameworks (Vue, Angular, etc.), specify a custom path like src/components.
Communicate the scope to each agent.
Spawn all 4 reviewer agents simultaneously using the Task tool. Each receives the scope and returns structured findings with file paths, line numbers, severity, and suggested fixes.
Agents:
- ux-clarity-reviewer — Missing feedback (loading, success, error, empty states)
- ux-consistency-reviewer — Behavioral inconsistency (tooltips, animations, patterns)
- recovery-reviewer — Dead-end error paths (missing retry, data loss, no escape)
- code-consistency-reviewer — Code pattern variance (prop naming, conventions)
Aggregation
Combine agent outputs: deduplicate same-file+line findings, sort by severity (HIGH → MEDIUM → LOW), group by file, track pattern frequency.
Report Format
Format findings for actionability:
# Polish Sweep Report
**Scope:** components/, app/ **Found:** X issues (Y high, Z medium)
## High Priority
### path/to/file.tsx
- **[clarity]** Line 45: Async operation without loading state → Add isLoading state,
show spinner during fetch
- **[recovery]** Line 78: Error caught but no user feedback → Show error toast with
retry option
## Medium Priority
### path/to/other-file.tsx
...
## Pattern Summary
| Issue Type | Count | Files |
| --------------------- | ----- | ----- |
| Missing loading state | 5 | 4 |
| Inconsistent tooltip | 3 | 3 |
| Dead-end error | 2 | 2 |
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.
- 25d ago First seen · 136 lines · 23 tokens per session scan A b10b14306308
polish-sweep is a command published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 23 tokens to every session and 911 once invoked, about $0.0001 per session on Opus 5.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-09-22.
Other commands, from other repositories
multi-frontend
Frontend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Gemini-led.
accessibility
You are the Accessibility (a11y) Specialist, ensuring applications are accessible to all users, including those with disabilities. You enforce WCAG standards and inclusive design principles.
contrato-ui
Bloquear estándares visuales antes de codear frontend (UI Design Contract).
plain-language-ui
You are the Plain-Language UI Specialist. You make every screen, field, button, and page in a web app explain itself to a first-day user with no domain training. Apps built fast from a PRD inherit the PRD's vocabulary — terms like Assujetti, UBO, eCDF, FAIA, PSF, matricule are precise in a spec and opaque on a screen…
a11y
You are a WCAG 2.1 Level AA accessibility specialist. You audit user interfaces for perceivable, operable, understandable, and robust compliance. You have zero tolerance for "we'll add a11y later" — accessibility is a launch requirement, not a polish step.
qa-design
UI/UX design audit and verification of web best practices.