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 lucasmaher-hash/touch-designer-mcp --skill vitepress-bilingual-pagegit clone --depth 1 https://github.com/lucasmaher-hash/touch-designer-mcpWrote 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/lucasmaher-hash/touch-designer-mcp/vitepress-bilingual-page)<a href="https://agentmods.dev/skills/lucasmaher-hash/touch-designer-mcp/vitepress-bilingual-page"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/vitepress-bilingual-page/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/lucasmaher-hash/touch-designer-mcp/vitepress-bilingual-page"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/vitepress-bilingual-page.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.00078 | $0.00781 |
| Opus 5 | $0.00039 | $0.00391 |
| Sonnet 5 | $0.00016 | $0.00156 |
| Haiku 4.5 | $0.00008 | $0.00078 |
Grade A, and why
vitepress-bilingual-page 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.
This is a copy
100% identical to vitepress-bilingual-page — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a page to the tdmcp VitePress site
The site lives under docs/, config in docs/.vitepress/config.ts
(base: "/tdmcp/", cleanUrls: true, deployed to
https://pantani.github.io/tdmcp/).
i18n convention — read this before deciding paths
Only the artist guide track is translated (EN + PT-BR). Everything else is English-only. The config encodes three nav groups:
artistGuide(base)/artistGuidePt→docs/guide/*.mdanddocs/pt/guide/*.md. This is the only mirrored track.devReference→docs/reference/*.md(English only).operations→ standalone pages likedocs/DEPLOYMENT.md,docs/ROADMAP.md(English only), plus external GitHub links.
So a privacy / legal page is NOT an artist-guide page. It belongs as a standalone page, English as the canonical version (legal text is fine in EN; the form needs exactly one privacy URL). Add a PT mirror only if the spec asks — do not force it just because the guide is bilingual.
Recommended placement for the privacy policy
- File:
docs/privacy.md→ clean URLhttps://pantani.github.io/tdmcp/privacy. - Frontmatter: give it a
title:(used bytransformHead) and consideraside: falsefor a legal page. - Nav: add to the
operationsarray inconfig.ts:{ text: "Privacy", link: "/privacy" }. (It's the legal/ops group, not the artist sidebar.) Put it near the end, before/after Changelog. - If a PT version is wanted:
docs/pt/privacy.md+ a{ text: "Privacidade", link: "/pt/privacy" }entry in the PT-side nav config.
The site uses
cleanUrls, so link to/privacy, never/privacy.html. For a page that needs a non-default URL (like DEPLOYMENT→deployment) you'd add arewritesentry — a lowercaseprivacy.mdneeds none.
How to verify a page is wired correctly
- The
.mdfile exists at the path whose URL you put in the nav. - The nav entry's
linkmatches the clean URL (no.md, no.html). npm run docs:buildpasses — VitePress fails the build on dead internal links, so a typo'd nav link or a broken in-page link is caught here. This is the gate; always run it after adding a page.- Loopback URLs (
localhost,127.0.0.1) in prose are ignored by the dead-link checker (seeignoreDeadLinks), so you can mention the bridge address freely.
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 · 58 lines · 78 tokens per session scan A fa4c9d13b5b6
vitepress-bilingual-page is a skill published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 781 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vitepress-bilingual-page, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications. Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.