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 vinvcn/addyosmani-agent-skills-zh --skill translate-skillgit clone --depth 1 https://github.com/vinvcn/addyosmani-agent-skills-zhWrote 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/vinvcn/addyosmani-agent-skills-zh/translate-skill)<a href="https://agentmods.dev/skills/vinvcn/addyosmani-agent-skills-zh/translate-skill"><img src="https://agentmods.dev/badge/skills/vinvcn/addyosmani-agent-skills-zh/translate-skill/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/vinvcn/addyosmani-agent-skills-zh/translate-skill"><img src="https://agentmods.dev/badge/skills/vinvcn/addyosmani-agent-skills-zh/translate-skill.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.00091 | $0.02547 |
| Opus 5.5 | $0.00036 | $0.01019 |
| Sonnet 5.5 | $0.00018 | $0.00509 |
| Haiku 4.5 | $0.00009 | $0.00255 |
Grade A, and why
translate-skill 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
翻译 skill
使用这个 skill 把上游 addyosmani/agent-skills 的内容翻译成简体中文,用于 vinvcn/addyosmani-agent-skills-zh。
这个 skill 用于内容本地化,不是 Git 同步。
操作原则
把用户可见的英文说明性文字翻译成自然的简体中文,同时原样保留所有行为关键内容。
目标仓库是一个独立的简体中文本地化版本。它应接收翻译后的内容,而不是上游的仓库元数据。
翻译哪些内容
翻译自然语言文本,包括:
README 说明
skill instructions
skill descriptions
用户可见的 frontmatter prompts
面向 agent 的指引
面向维护者的指引
docs 说明性文字
以说明性文字写成的示例
Markdown 标题(headings)
Markdown 标题的翻译规则
标题是说明性文字,翻译成简体中文;标题层级与 Markdown 结构保持不变。标题内嵌的 inline code、identifiers 原样保留。
- docs 页面与 skill 文件的固定 schema 标题必须使用
TRANSLATION-GLOSSARY.md登记的统一译法,保证所有页面一致。 - 其余标题按页面语境意译,无需逐一登记。
- 例外(作为术语保留英文,不译):模板结构标题(如 spec/ADR 模板内的
Objective、Tech Stack、Status等,与上游模板逐字一致);invocation 术语(User-invoked、Model-invoked)。 - 修改标题时,同步更新同一文件内指向该标题的 anchor links(GitHub 会按标题文本生成 slug,中文标题生成中文 anchor)。仓库用
node scripts/validate-reference-links.js强制这一条。
原样保留哪些内容
不要翻译或改写:
目录名
skill 名称
slash commands
CLI 命令
代码块
inline code
文件路径
package 名
tool identifiers
API identifiers
环境变量名
frontmatter keys
JSON/YAML/TOML keys
Markdown 链接 URL
行为关键 labels
保持 Markdown 结构、标题层级、列表嵌套、表格、链接目标、相对路径和 code fences 不变。
仓库路径本地化
翻译用户可见的安装示例时,把上游仓库路径:
addyosmani/agent-skills
替换为本地化仓库路径:
vinvcn/addyosmani-agent-skills-zh
只有当命令或说明性文字是在告诉用户如何安装或使用本地化仓库时,才做这个替换。
不要移除对上游项目的署名。
Frontmatter 规则
原样保留 frontmatter keys。
按含义而不仅是字段名,对每个 frontmatter 值分类:
- 保持
name值不变。 - 把用户可见或面向 agent 的自然语言文本翻译成简体中文,包括
description和argument-hint的值。 - 保持 identifiers、命令、路径、package 名、URL、工具名、布尔值、数字和其他有类型的配置值不变。
- 在可翻译的值内部,原样保留内嵌的 slash commands、inline code、占位符、路径、URL、package 名、工具名和其他行为关键片段。
- 对有歧义的值打复核标记,不要猜测。
示例:
---
name: teach
description: 在这个工作区中教用户一个新技能或概念。
disable-model-invocation: true
argument-hint: "你想学习什么?"
---
翻译风格
使用满足以下要求的简体中文:
自然
对开发者友好
简洁
准确
与本仓库现有语气一致
如果某个常见工程术语在开发者中是标准说法,或者翻译它会降低清晰度,就把它保留为英文。
术语参考
查阅仓库根目录的 TRANSLATION-GLOSSARY.md。
对已决定的术语,严格使用记录的译法。
术语决定与落地流程
术语的请求与认领流程见 CONTRIBUTING.md;译法以 TRANSLATION-GLOSSARY.md 为唯一权威。一次完整的落地流程:
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 Changed · +57 lines · +11 tokens per session ee4f879d2091
- 1mo ago First seen · 180 lines · 80 tokens per session scan A 7d01f1a80f47
translate-skill is a skill published in the GitHub repository vinvcn/addyosmani-agent-skills-zh (44 stars, last pushed 7d ago), licensed MIT. It adds 91 tokens to every session and 2,547 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
i18n
Audit internationalization coverage and find hardcoded strings. Use when asked to "check i18n", "find hardcoded strings", or verify translation coverage. Don't use for backend code, projects without an i18n library, accessibility (/a11y-audit), or bundle size (/perf-audit).
test-driven-development
Drives development with tests via Red-Green-Refactor and the Prove-It pattern, with hard rules against weakening assertions or faking green suites. Use when implementing any logic, fixing any bug, or changing any behavior. Triggers on "add a feature", "fix this bug", "write tests", or any task where done must be…
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
data-engineering
Guides data pipeline design, ETL/ELT workflows, schema evolution, and data quality assurance. Use when building data pipelines, designing data warehouses, migrating schemas, or ensuring data integrity across systems. Use when you need reliable, testable, and observable data flows.
debugging-and-error-recovery
Guides systematic root-cause debugging with hard rules against guess-fixes and symptom suppression. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Triggers on "this is broken", "tests are failing", "why doesn't this work", or any error output.