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/lenoseibert/semver-plugin/sync-readmesnpx skills add LenoSeibert/semver-plugin --skill sync-readmesgit clone --depth 1 https://github.com/LenoSeibert/semver-pluginWhat 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.00046 | $0.00409 |
| Opus 5 | $0.00023 | $0.00204 |
| Sonnet 5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
sync-readmes 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 yesterday.
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
Sync the README translations
README.md at the repository root is canonical. The four translations must
mirror it:
docs/README.es.md— Spanishdocs/README.hi.md— Hindidocs/README.pt-BR.md— Brazilian Portuguesedocs/README.zh-CN.md— Simplified Chinese
$ARGUMENTS may name specific locales to sync. If empty, sync all four.
Steps
- Determine what changed in
README.md. Prefer the real diff (git diff -- README.md, orgit log -p -1 -- README.mdif it is already committed) over re-reading the whole file — this is a propagation task, not a re-translation. - For each target file, apply the equivalent change in that language. Translate
prose; do not translate code blocks, command names, file paths, flags,
environment variables, or
maketargets. - Keep the structure identical to the canonical file: same section order, same emoji in headings, same links, same badges, same relative asset paths. The table-of-contents anchors must match the translated heading text in that file.
- Keep Markdown hard-wrapped at ~80 columns, matching the rest of the repo.
- If a section exists in
README.mdbut is missing from a translation, add it rather than skipping — report any section you could not confidently translate instead of guessing. - Run
make check-diffto catch whitespace errors.
Report which files you changed and any content you deliberately left in English.
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.
- yesterday First seen · 40 lines · 46 tokens per session scan A 5b2a1c1b5c7c
sync-readmes is a skill published in the GitHub repository LenoSeibert/semver-plugin (1 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 409 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-31.
Other skills, from other repositories
kagi-summarizer
Summarize any URL or text using Kagi's Universal Summarizer API. Supports multiple engines (including the enterprise-grade Muriel model), bullet-point takeaways, and output translation to 28 languages. Use when you need a high-quality summary of an article, paper, video transcript, or any document.
i18n
Internationalization (i18n) workflow and standards for managing translations. Use when: (1) Adding new user-facing text, (2) Creating new components with user-facing text, (3) Reviewing code for i18n compliance, (4) Adding a new translation module.
lov-image-translation-errata
核对截图中的原文与机翻，生成保留错误痕迹、给出正确译文且尽量维持原布局的勘误图；用于“图片翻译勘误”“指出机翻错误”和 create an in-image translation errata。.
lov-academic-translator
将英文论文、arXiv、期刊/会议文章及技术 PDF 翻译为中文 PDF 或可发布的中文 Markdown。用户提出“翻译英文 PDF”“翻译论文”“论文超级翻译官”“保留图片、公式和原版式”“原文译文对照”“页数对应”或“PDF 图文排版不要乱”时使用。.
tech-to-marketing-brief
将零散的技术特性和算法更新，转化为完整的运营 Brief、社媒宣发案例库以及配套的研发 Jira Ticket.
spec-authoring
G2 — translate a numbered acceptance-criteria list (AC-1, AC-2, ...) from pipeline/brief.md into Gherkin scenarios in pipeline/spec.feature. One Scenario per AC, tagged @AC-N. Drives stage-03b (executable-spec) and enables zero-drift mapping through QA.