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/sigistry/marketplaceWrote 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/sigistry/marketplace/rtl-ready)<a href="https://agentmods.dev/commands/sigistry/marketplace/rtl-ready"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/rtl-ready.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.00013 | $0.00833 |
| Opus 5 | $0.00006 | $0.00417 |
| Sonnet 5 | $0.00003 | $0.00167 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
rtl-ready 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 6d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit the styles and components in $ARGUMENTS (or the current diff) for right-to-left readiness, and rewrite direction-hardcoded CSS into logical, bidi-safe equivalents. Most "we don't support Arabic/Hebrew yet" debt is a pile of physical left/right properties that a mechanical rewrite fixes safely; the rest is a short list of things that genuinely need human eyes. Load the catalog-hygiene skill's references/rtl-logical-properties.md for the property map and pitfalls.
Process
Step 1: Scope the styles
Read the target CSS/SCSS/Less, CSS-in-JS, Tailwind classes, and inline styles. Note whether the project already sets dir="rtl" anywhere, uses logical properties at all, or relies on a bidi library, this tells you whether you are starting a retrofit or finishing one.
Step 2: Find physical, direction-hardcoded properties
Grep for the physical properties and flag each with file:line:
| Physical (LTR-baked) | Logical (direction-aware) |
|---|---|
margin-left / margin-right |
margin-inline-start / margin-inline-end |
padding-left / padding-right |
padding-inline-start / padding-inline-end |
left / right (offsets) |
inset-inline-start / inset-inline-end |
text-align: left / right |
text-align: start / end |
border-left / border-right |
border-inline-start / border-inline-end |
float: left / right |
float: inline-start / inline-end |
border-radius per-corner |
border-start-start-radius etc. |
Step 3: Flag the things logical properties can't fix
These need judgment, not a find-replace, list them as caveats, do not blindly flip:
- Directional icons: back/forward/next arrows, chevrons, send icons must mirror; decorative or brand icons (a checkmark, a logo) must not.
- Transforms:
translateX,transform-origin, and skews may need[dir="rtl"]overrides. - Box shadows / gradients with an x-offset that implies a light direction.
- Bidi text: user content mixing scripts needs
dir="auto"/ Unicode isolation (<bdi>), not CSS. - Background-position and sprite offsets keyed to a side.
- Keyline borders and animations that slide from a specific edge.
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.
- 6d ago First seen · 48 lines · 13 tokens per session scan A 31643d7854ca
rtl-ready is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 833 once invoked, about $0.0001 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-31.
Other commands, from other repositories
dashboard-layout
Design and build a complete dashboard layout — sidebar navigation, KPI cards, chart areas, data tables, filter bar, and responsive behavior. Outputs production-ready HTML/CSS.
design-audit
Audit an existing HTML/CSS design. Deterministic checks only (contrast, fonts, colors, states, dark mode) plus a visual pass. No generation.
design
Full design pipeline for a web or web-app target: brief → tokens → generation → motion → review. Use /design:mobile for iOS/Android instead.
wp-tailwindify
Convert an HTML/CSS demo to Tailwind-native HTML — preserves section delimiters, maps colors to @theme variables.
wp-responsive-check
Responsive validation — screenshots at 5 viewports, checks for layout issues.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.