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 skills add aiya000/dotfiles --skill sync-translated-docsgit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/skills/aiya000/dotfiles/sync-translated-docs)<a href="https://agentmods.dev/skills/aiya000/dotfiles/sync-translated-docs"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-translated-docs/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/skills/aiya000/dotfiles/sync-translated-docs"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-translated-docs.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.00085 | $0.01287 |
| Opus 5.5 | $0.00034 | $0.00515 |
| Sonnet 5.5 | $0.00017 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00129 |
Grade A, and why
sync-translated-docs 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sync-translated-docs
A translated pair is one document written twice, not two documents. A reader picks whichever language they read and expects the same thing to be there.
Editing one half and stopping is the failure this skill exists to prevent. The two drift apart quietly -- nothing fails to build, no test goes red -- and the drift is only ever noticed by a reader who cannot read the other half to compare.
When this skill does not apply
No counterpart, no skill. A repository whose only readme is README.md, with no README_JP.md
or any other translation beside it, is outside this skill entirely -- edit the one file and say
nothing about translations.
Do not read this as a suggestion to create the missing half. Whether a project is translated at all is the user's decision, not something to infer from the absence of a file. Only offer to add a translation if the user asks for one.
Finding the counterpart
A file has a counterpart when another file differs from it only by a language marker:
README.md↔README_JP.md/README.ja.md/README-ja.mddocs/guide.md↔docs/guide_JP.md/docs/ja/guide.mdCONTRIBUTING.md↔CONTRIBUTING_JP.mdCODE_OF_CONDUCT.md↔CODE_OF_CONDUCT_JP.md
A hook says so after the fact, but do not wait for it. ~/.claude/hooks/remind-translated-counterpart.sh
runs after every markdown write and names the counterpart when one is beside the file. It is the net,
not the plan: being told afterwards means the edit is already half-done. It follows the same rule as the
section above -- silent when no counterpart exists -- so read its silence as "this file has no pair",
never as "nobody checked".
Check for one before editing, not after. ls the directory, or fd 'README'. If the pair
exists, both files are in scope from the start -- treat "update the README" as "update both READMEs".
If it does not exist, stop here: the section above applies.
The rule
Both halves change in the same commit. Never leave one for later: "later" is where the drift lives.
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.
- 1mo ago Changed · +7 lines d8f78c72920b
- 1mo ago First seen · 111 lines · 85 tokens per session scan A 17bbf9a0d631
sync-translated-docs is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 14d ago), licensed MIT. It adds 85 tokens to every session and 1,287 once invoked, about $0.0003 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-11.
Other skills, from other repositories
restart__pull_request
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
validate__japanese
A Japanese-language review for Markdown documents, such as READMEs, manuals, and blog drafts. It checks writing style, spacing, line breaks, and links to real code symbols.
rescue__pull_request_review
An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.
submit__pull_request
An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.
write__pull_request
A workflow for writing a pull request description, the explanation attached to a proposed code change for review. It analyses the changes and commit history.
monitor__ci_status
An automated monitor for GitHub Actions, the service that runs checks such as tests after code changes. It watches all checks after a pull request or a push to a pull-request branch and can invoke a failure-recovery process.