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/f0d010c/stark/stark-translategit clone --depth 1 https://github.com/f0d010c/starkWrote 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/f0d010c/stark/stark-translate)<a href="https://agentmods.dev/commands/f0d010c/stark/stark-translate"><img src="https://agentmods.dev/badge/commands/f0d010c/stark/stark-translate.svg" alt="Measured on agentmods" 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.00050 | $0.00472 |
| Opus 5 | $0.00025 | $0.00236 |
| Sonnet 5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
stark-translate 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 5d 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
/stark-translate
Legacy Claude Code command. In Codex, ask:
Translate this Apple UI to Windows using stark.
Translate UI from $1 (source platform) to $2 (target platform), preserving product semantics but using the target platform's idiom.
Source/target must each be one of: web, windows, apple, android.
Process
-
Read the source — file content or description from
$ARGUMENTSafter the platform args. -
Identify the product semantics — what is this UI doing? Settings? List-detail? Onboarding? Tab nav? Modal flow?
-
Translate idiom, not pixels. Reference the translation rules in
skills/cross-platform-design/SKILL.mdstep 3.Example: an iOS grouped Form with switch toggles becomes:
- On Windows →
NavigationView+ scrollable stack ofSettingsCardover Mica - On Android →
LargeTopAppBar+LazyColumnwithListItemrows + M3 switches - On web → asymmetric layout with sidebar nav and editorial section headers
- On Windows →
-
Apply target platform's anti-slop ban list as you generate. Read the target's SKILL.md step 6.
-
State the translation choices at the top of the response in 2–3 lines:
- "iOS grouped Form → Windows NavigationView + SettingsCard stack with Mica backdrop"
- "iOS Toggle → WinUI ToggleSwitch with ThemeResource brushes"
- "iOS section headers → Windows muted text headers, no row separators"
-
Implement working code in the target stack.
Refuse to pixel-clone. If the user insists on identical pixels across platforms, push back once with the rationale: every platform has reference apps that nail their idiom; users notice when a Mac app feels Android.
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.
- 5d ago First seen · 40 lines · 50 tokens per session scan A 2fb7b2dbe8f3
stark-translate is a command published in the GitHub repository f0d010c/stark (25 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 472 once invoked, about $0.0003 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
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.
design-triage
Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.
auth-implementation
Use when a project needs real working login and signup rather than advice. Wiring up Clerk or Supabase Auth, protecting routes, handling sessions. Writes actual code, not guidance.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.