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 xyy277/doc77 --skill doc-translationgit clone --depth 1 https://github.com/xyy277/doc77Wrote 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/xyy277/doc77/doc-translation)<a href="https://agentmods.dev/skills/xyy277/doc77/doc-translation"><img src="https://agentmods.dev/badge/skills/xyy277/doc77/doc-translation.svg" alt="Measured on agentmods" 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.00048 | $0.00304 |
| Opus 5 | $0.00024 | $0.00152 |
| Sonnet 5 | $0.00010 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
doc-translation 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 8d 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.
What it actually says
文档翻译技能
翻译原则
- 保持原文的 Markdown 格式（标题、列表、代码块、链接）
- 技术术语优先使用行业标准译法
- 代码块内容不翻译（仅翻译注释）
- URL 和文件路径不翻译
- 保持原文的段落结构和列表层级
术语处理
- 首次出现的术语：中文翻译（英文原文）
- 后续出现：仅用中文翻译
- 无标准译法的术语保留英文
翻译方向
- 中 → 英：使用自然流畅的英语表达，避免中式英语
- 英 → 中：使用规范的中文技术文档风格，避免翻译腔
特殊处理
- 表格：保持结构，翻译单元格内容
- frontmatter：翻译 description 等字段，保留 key 名
- 代码注释：翻译为目标语言
- 错误信息：保留原始错误码，翻译描述
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.
- 8d ago First seen · 32 lines · 48 tokens per session scan A 5f9bcc803c82
doc-translation is a skill published in the GitHub repository xyy277/doc77 (8 stars, last pushed 19d ago), licensed MIT. It adds 48 tokens to every session and 304 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
diagrams
Mermaid diagrams following the C4 model: context, container, component, sequence, ER and deployment. Use when saying "diagram", "visualize", or "architecture diagram".
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
suiko
A Japanese writing and review workflow for checking whether text sounds uniform, translated, unnatural, or difficult to read. It supports writing and editing documents such as reports, guides, meeting notes, proposals, and emails.