claude-sdk-rs: Command for Claude Code

.claude/commands/define-polish-standard.md

define-polish-standard is a command for Claude Code from bredmond1019/claude-sdk-rs. It costs 0 tokens per session (2,829 once invoked), scanned A, original, Apache-2.0.

A command that writes a review standard for judging whether a user interface looks and works as intended. It can define separate standards for web, mobile, terminal, or desktop interfaces.

In plain words
What is it for?
Use it to create or extend a standard for assessing a product's screens and interface quality.
Why use it?
It replaces vague opinions about a polished interface with written criteria that reviewers can apply consistently.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents.

This is bredmond1019/claude-sdk-rs's own configuration. It tells Claude Code how to work on claude-sdk-rs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-sdk-rs configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bredmond1019/claude-sdk-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/bredmond1019/claude-sdk-rs/main/.claude/commands/define-polish-standard.md
Clone the repo
git clone --depth 1 https://github.com/bredmond1019/claude-sdk-rs

Made for: Claude Code.

Wrote 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.

agentmods badge for define-polish-standard

README.md
[![agentmods](https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/define-polish-standard/github.svg)](https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/define-polish-standard)
Your own site
<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/define-polish-standard"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/define-polish-standard/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.

agentmods 80×15 button for define-polish-standard

Your own site · 80×15
<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/define-polish-standard"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/define-polish-standard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,829 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02829
Opus 5.5 $0.00000 $0.01132
Sonnet 5.5 $0.00000 $0.00566
Haiku 4.5 $0.00000 $0.00283

Measured 11d ago against content hash ca922632c424, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

define-polish-standard 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 11d 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.

.claude/commands/define-polish-standard.md · 247 lines

How it starts

The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Define Polish Standard — write the document a UI can actually be judged against.

Variables

$ARGUMENTS — what the standard covers, plus flags. Example: "the BastionUI operator app --surface mobile --slug surfaces-e2e"

Flag What it does
--surface <web|mobile|tui|desktop> The surface kind. Repeatable — a product with a web app and a phone app gets one section per surface, because the rules differ
--slug <name> Output goes to planning/<name>/polish-standard.md. Default: kebab-case of the description
--from <path> An existing standard, style guide, or design doc to build on rather than replace
--no-calibrate Skip the two-agent calibration. Only for a throwaway draft — never before an assessment reads it

Purpose

"Clean and polished" cannot be assessed against nothing. Without a written standard you get opinions; opinions differ between reviewers; and opinions do not become blocks of work.

This command writes planning/<slug>/polish-standard.md: a falsifiable description of what good looks like for this specific product, specific enough that two people shown the same screenshot reach the same verdict.

It is the input a UI review reads — /assess's polish scout, a /ticket's acceptance criteria, a reviewer's checklist. It is not a design system, a brand guide, or a redesign.

The test this document must pass: hand it plus one screenshot to two fresh agents and ask "does this pass?" If they disagree, the standard is not finished. That is step 6, and it is the point of the command.

Instructions

  1. If $ARGUMENTS is empty, stop and ask what surface to write a standard for.

  2. Resolve the surfaces. Take them from --surface, or infer from the repo and confirm with the user before writing. Each named surface gets its own section — the rules genuinely differ, and a merged section produces items that are meaningless for one of them (touch targets on a TUI, hover states on a phone).

Read the full file on GitHub · 247 lines

Changes

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.

  1. 11d ago First seen · 247 lines · 0 tokens per session scan A ca922632c424

Subscribe to this mod's changes

define-polish-standard is a command published in the GitHub repository bredmond1019/claude-sdk-rs (23 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,829 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-10-26.

Related

define-polish-standard compared with commands from other repositories

define-polish-standard next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
define-polish-standardbredmond1019/claude-sdk-rsCommand231mo agoApache-2.0A0Claude Code
pr-enhanceruvnet/rufloCommand81ktodayMITA0Claude Code
test-featureLykhoyda/rn-dev-agentCommand2012d agoMITA30Claude Code
test-value-reviewoalders/kitchen-sinkCommand53d agoMITA58Claude Code
bug-checkyeaight7/agent-powerupsCommand81mo agoApache-2.0A25Claude Code
claude-looprunnithan/claudex-setupCommand111d agoMITB72Claude Code
security-sastzsutxz/ClaudeLearningCommand53mo agoMITA17Claude Code