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.00080 | $0.01116 |
| Opus 5 | $0.00040 | $0.00558 |
| Sonnet 5 | $0.00016 | $0.00223 |
| Haiku 4.5 | $0.00008 | $0.00112 |
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 12d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Translate Skill
Use this skill to translate upstream mattpocock/skills content into Simplified Chinese for vinvcn/mattpocock-skills-zh-CN.
This skill is for content localization, not Git synchronization.
Operating principle
Translate user-facing English prose into natural Simplified Chinese while preserving all behavior-critical content exactly.
The target repo is an independent Simplified Chinese localized edition. It should receive translated content, not upstream repository metadata.
What to translate
Translate natural-language prose, including:
README explanations
skill instructions
skill descriptions
agent-facing guidance
maintainer-facing guidance
docs prose
examples that are written as prose
What to preserve exactly
Do not translate or rewrite:
directory names
skill names
slash commands
CLI commands
code blocks
inline code
file paths
package names
tool identifiers
API identifiers
environment variable names
frontmatter keys
JSON/YAML/TOML keys
Markdown link URLs
behavior-critical labels
Preserve Markdown structure, heading levels, list nesting, tables, link targets, relative paths, and code fences.
Repository-path localization
When translating user-facing installation examples, replace the upstream repo path:
mattpocock/skills
with the localized repo path:
vinvcn/mattpocock-skills-zh-CN
Only make this replacement where the command or prose is telling users how to install or use the localized repo.
Do not remove attribution to the upstream project.
Frontmatter rules
Preserve frontmatter keys exactly.
For frontmatter values:
- Keep
namevalues unchanged. - Keep identifiers, commands, paths, package names, URLs, and tool names unchanged.
- Translate
descriptiononly when it is natural-language prose. - Flag ambiguous values rather than guessing.
Translation style
Use Simplified Chinese that is:
natural
developer-friendly
concise
accurate
consistent with existing repo tone
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.
- 12d 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 (31 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 1,116 once invoked, about $0.0004 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
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…
ai-ops
Guides operational excellence for AI/ML systems in production. Use when deploying models, managing inference infrastructure, monitoring model drift, or maintaining AI-powered features. Use when you need reliable, observable, and governable machine learning systems.
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.