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 skills/rilldata/rill/i18n-migratenpx skills add rilldata/rill --skill i18n-migrategit clone --depth 1 https://github.com/rilldata/rillWhat 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.00032 | $0.00909 |
| Opus 5 | $0.00016 | $0.00454 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
i18n-migrate 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 2d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit the changes on the current branch for hardcoded user-facing strings that should be moved to i18n (Paraglide/inlang messages), following the conventions in web-common/src/lib/i18n/README.md.
Optional focus: $ARGUMENTS
Instructions
1. Determine the diff to audit
- If
$ARGUMENTSlists files or directories, scope the audit to those paths only. - Otherwise, audit the PR diff:
git diff --merge-base mainto get changed lines across the branch. - Only consider added or modified lines. Do not flag pre-existing strings unless the file was explicitly passed in
$ARGUMENTS. - Only frontend files are in scope:
web-common/,web-admin/,web-local/, with extensions.svelteand.ts/.svelte.ts.
2. Find hardcoded user-facing strings
Mirror the heuristics in scripts/i18n-guard.js:
- Svelte visible text: content between
>and<that contains real words. - Human-facing attributes:
placeholder,title,aria-label,alt,label. - TypeScript: string literals used as user-facing copy — e.g.
label:,header:,body:, toast/notification text, thrown error messages shown to users, option arrays.
Skip (not user-facing): identifiers, URLs, paths, CONSTANT_CASE, class/style names, object keys, console.*/log messages, code comments, test files (*.spec.ts, *.test.ts, e2e), and lines with an i18n-ignore comment on or above them.
3. Propose keys, reusing what exists
For each finding, before proposing a new key, grep web-common/src/lib/i18n/messages/en.json for the exact copy — reuse an existing key if one matches (especially common_*).
When a new key is needed, follow the README conventions:
- Naming:
feature_component_purpose, lower snake_case, grouped by prefix. common_*for copy reused across features; otherwise prefix with the feature directory name.- Generic shared components (in
web-common/src/components/) should usecommon_*keys, not feature-specific ones. - Interpolation: named placeholders, never string concatenation —
"Sort by {label}", not"Sort by " + label. - Pluralization: use Paraglide variants, not
count === 1 ? ... : ....
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.
- 2d ago First seen · 59 lines · 32 tokens per session scan A 07e60e936631
i18n-migrate is a skill published in the GitHub repository rilldata/rill (2,859 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 909 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 skills, from other repositories
hardwood-pr-git
Rebase, rewrite, squash, reword and push Hardwood PR history — including contributor PRs whose author and committer identity must survive the rewrite. Use whenever the user asks to "rebase", "rebase onto main", "fix the commit message", "prefix with the issue key", "squash the commits", "force push (with lease)"…
hardwood-cli
Inspect, debug, and convert Apache Parquet files with the hardwood CLI. Use whenever a user is debugging code that reads or writes Parquet (Arrow / Spark / Flink / Java / Python) and the data file itself may be the cause — to check the schema, physical and logical types, repetition, or a row sample. Use it to diagnose…
hardwood-review
Review a Hardwood PR, local branch, or staged diff against the project's CLAUDE.md conventions and recurring failure modes. Use whenever the user asks to "review", "look over", "check", "audit", or "assess" a PR number, a branch, or pending changes in the hardwood-hq/hardwood repo. Also use when the user pastes a PR…
hardwood-address-review
Work through a reviews/pr- -review.md findings file against a Hardwood PR — check out the PR branch, make the fixes, surface each Decision with its options + recommendation for the maintainer to pick, tick off addressed items in the review file, and commit (do not push). Use whenever the user says "address review for.
parquet-dev-ml
Search the Apache parquet-dev mailing list by downloading the raw monthly mbox archives from lists.apache.org and grepping them locally. Use whenever the user wants to find, read, or quote a thread on the Parquet dev list ([email protected]) — e.g. "search the parquet-dev ML", "find the thread about X on the…
exasol-import-export
Exasol IMPORT and EXPORT SQL statements: syntax, file formats (CSV, FBV, Parquet), cloud storage (S3, Azure, GCS), connection objects, error handling, and ETL staging patterns.