Borrowing it
Nothing to install: this file belongs to mmadfox/swag2mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mmadfox/swag2mcp/main/.agents/skills/swag2mcp-doc-writer/SKILL.mdgit clone --depth 1 https://github.com/mmadfox/swag2mcpWrote 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/mmadfox/swag2mcp/swag2mcp-doc-writer)<a href="https://agentmods.dev/skills/mmadfox/swag2mcp/swag2mcp-doc-writer"><img src="https://agentmods.dev/badge/skills/mmadfox/swag2mcp/swag2mcp-doc-writer/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/mmadfox/swag2mcp/swag2mcp-doc-writer"><img src="https://agentmods.dev/badge/skills/mmadfox/swag2mcp/swag2mcp-doc-writer.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.00055 | $0.02827 |
| Opus 5.5 | $0.00022 | $0.01131 |
| Sonnet 5.5 | $0.00011 | $0.00565 |
| Haiku 4.5 | $0.00006 | $0.00283 |
Grade A, and why
swag2mcp-doc-writer 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 2mo 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swag2mcp-doc-writer — Documentation Writing Skill
When this skill activates
Activate when the user asks to write, edit, add, remove, or restructure any documentation file in the docs/ directory. This includes:
- Creating new pages or sections
- Updating existing content (commands, flags, config fields, examples)
- Adding or removing files
- Renaming or moving files
- Updating the VitePress config (
config.mjs)
Critical Rule: Multi-Language Consistency
The documentation is maintained in 8 locales. The root docs/ directory is English. Every change to an English file MUST be replicated identically to all 7 translated locales:
| Locale | Directory | Prefix |
|---|---|---|
| English (default) | docs/ |
/ |
| Russian | docs/ru/ |
/ru/ |
| German | docs/de/ |
/de/ |
| French | docs/fr/ |
/fr/ |
| Spanish | docs/es/ |
/es/ |
| Chinese | docs/zh-CN/ |
/zh-CN/ |
| Japanese | docs/ja/ |
/ja/ |
| Korean | docs/ko/ |
/ko/ |
Synchronization rules
- File structure is identical across all locales — same subdirectories, same filenames, same number of files
- Content is copied as-is from English to all locales. Translation is done separately — the skill only ensures structural consistency
- When adding a file — create it in English first, then copy to all 7 locale directories
- When deleting a file — remove from English and all 7 locale directories
- When renaming a file — rename in English and all 7 locale directories, then update all links in
config.mjsand all.mdfiles that reference the old path - When updating content — update the English file, then copy the exact same content to the corresponding file in each locale directory
config.mjs— only one file exists atdocs/.vitepress/config.mjs. It contains sidebar and nav definitions for all 8 locales. Update it once.
Verification command
After any change, run:
npm run docs:build
The build must complete without errors. If it fails, fix the issues before reporting success.
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.
- 2mo ago First seen · 353 lines · 55 tokens per session scan A 0dd0032766d2
swag2mcp-doc-writer is a skill published in the GitHub repository mmadfox/swag2mcp (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,827 once invoked, about $0.0002 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-31.
Other skills, from other repositories
omh-localization-review
This is an OMH localization-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
humanizer-zh
A Chinese-language editing guide for making AI-written fiction sound more natural and consistent in wording and punctuation.
localization-design
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use ux-writing (designer-toolkit).
i18n-localization
Implement localization with translated messages, locale-aware formatting and adaptable layouts. Use when supporting multiple languages, RTL or regional formats; preserve message identity and test realistic translated content rather than only replacing labels.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
i18n-check
An internationalization (i18n) check for software that supports multiple languages. It compares translation files with the text and translation keys used by the code.