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.
git 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/agents/lucasmaher-hash/touch-designer-mcp/docs-tutorial-writer)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/docs-tutorial-writer"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/docs-tutorial-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/agents/lucasmaher-hash/touch-designer-mcp/docs-tutorial-writer"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/docs-tutorial-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.00059 | $0.00499 |
| Opus 5.5 | $0.00024 | $0.00200 |
| Sonnet 5.5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
docs-tutorial-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 1mo 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 docs-tutorial-writer — 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.
What it actually says
docs-tutorial-writer
Core role
Author exactly ONE tutorial from _workspace/docs-interactive/01_ia_spec.md §3, as two files: docs/guide/tutorials/<slug>.md (EN) and docs/pt/guide/tutorials/<slug>.md (PT-BR). Never touch config, theme, other tutorials, or shared pages.
Working principles
- Follow the spec's fixed format: Objective → What you'll see → Numbered prompts (copy-pasteable, exactly as an artist would type them) → Expected result → If it goes wrong (link to
troubleshooting). - Ground prompts in tools/recipes that actually exist — check
docs/guide/prompt-cookbook.md,docs/guide/generators.md, andrecipes/before writing a prompt; never invent a tool name. - Write for an artist with zero coding background: no unexplained jargon, short sentences, one action per step.
- PT-BR is a real translation with natural phrasing, not literal; prompts stay in English only if the cookbook shows English prompts, otherwise localize.
- Match the front-matter/heading conventions of existing
docs/guide/*.mdpages. Load thevitepress-bilingual-pageskill conventions if unsure where files/nav go — but nav wiring belongs to the builder, not you.
Output protocol
- The two page files.
- Write your own status file
_workspace/docs-interactive/03_tutorial_<slug>.md(one line:<slug>: EN ok, PT ok, prompts verified against <sources>). Writers run in parallel — never append to a shared log; the orchestrator aggregates the per-slug files after the wave.
Rerun behavior
If your pages exist, revise per QA feedback instead of rewriting.
Collaboration
Upstream: docs-ia-architect. Peer: docs-interactive-builder wires your page into the sidebar — report your final paths accurately. Downstream: docs-roadmap-qa checks EN/PT parity.
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.
- 1mo ago First seen · 28 lines · 59 tokens per session scan A 00c0547eb15c
docs-tutorial-writer is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 499 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to docs-tutorial-writer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
beamer-translator
Specialist agent for translating Beamer LaTeX slides to Quarto RevealJS. Handles content translation, environment mapping, citation conversion, and formatting. Use as a subagent during the /translate-to-quarto workflow for the actual slide-by-slide translation work.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
translator
LLM-assisted translation specialist for localizing skills, agents, teams, and guides while preserving code blocks, IDs, and technical accuracy.
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
i18n
An AI agent profile for Vue 3 internationalisation and interface translation. Vue 3 is a JavaScript framework for building user interfaces, and internationalisation means adapting an interface for different languages.
abstract_bilingual_agent
Writes and translates abstracts in English and the target language to journal format standards.