markdown-mdx-content-pipeline-wasp-drone — Claude Code subagent
markdown-mdx-content-pipeline-wasp-drone — a subagent for building and reviewing Markdown/MDX pipelines from source files to HTML, JSX, or React output. Use it for compilers, plugin chains, highlighting, math, diagrams, and sanitization.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install documentation-tools@wasp-nestWhat markdown-mdx-content-pipeline-wasp-drone does
This subagent covers the path from .md and .mdx files to rendered HTML, JSX, or React output. It can help choose Velite, @next/mdx, or @mdx-js/mdx, arrange remark and rehype stages, configure GFM, work with ASTs, and set up Shiki v4, expressive-code, or starry-night.
It also handles typed custom plugins, KaTeX math, Mermaid and D2 diagrams, plus rehype-sanitize and DOMPurify. For a new pipeline, it can outline fixtures and XSS checks. The plugin order matters: rehypeSanitize must follow rehypeRaw, or raw HTML can reach the next stage without the intended filtering.
The subagent runs with Claude Code and Codex. User-authored Markdown requires sanitization settings; documentation-platform choice and the mdx-components.tsx component map belong to other subagents.
What it helps with
- choose a compiler for Markdown and MDX
- assemble a remark and rehype plugin chain
- configure code highlighting with Shiki v4
- add KaTeX formulas and Mermaid diagrams
- filter unsafe HTML from user-authored Markdown
Example prompts for the agent
- Set up an MDX processing pipeline for this project and recommend a compiler.
- Review the remark and rehype order, then fix the sanitization setup.
- Add KaTeX formulas and Mermaid diagrams to the Markdown pipeline and create tests.
How to install markdown-mdx-content-pipeline-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install documentation-tools@wasp-nest2Manually: put the files in place
.claude/agents/markdown-mdx-content-pipeline-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/markdown-mdx-content-pipeline-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/markdown-mdx-content-pipeline-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about markdown-mdx-content-pipeline-wasp-drone
How do I install markdown-mdx-content-pipeline-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then run /plugin install documentation-tools@wasp-nest. Add .claude/agents/markdown-mdx-content-pipeline-wasp-drone.md afterward.
What does markdown-mdx-content-pipeline-wasp-drone do?
It builds and reviews Markdown/MDX processing pipelines, covering compiler choice, remark and rehype stages, code highlighting, math, diagrams, and HTML sanitization.
Which work is outside this subagent's scope?
Documentation-platform selection goes to docs-site-wasp-drone, while the mdx-components.tsx component map goes to react-wasp-drone. Broader XSS audits are outside its sanitization-configuration scope.