docusaurus-expert

A specialized assistant for Docusaurus, a tool for building documentation websites from Markdown and code.

In plain words
What is it for?
It is for configuring documentation sites, writing pages, organizing sidebars, changing themes, and fixing deployment or build issues in the specified folder.
Why use it?
It helps diagnose setup and build problems without requiring you to know Docusaurus configuration and theming details.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/albert-mr/genlayer-mcp-server/docusaurus-expert
Clone the repo
git clone --depth 1 https://github.com/albert-mr/genlayer-mcp-server

Made for: Claude Code.

Per session 294 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 717 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00294 $0.00717
Opus 5 $0.00147 $0.00358
Sonnet 5 $0.00059 $0.00143
Haiku 4.5 $0.00029 $0.00072

Measured 2d ago against content hash 08ab2a2a8379, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docusaurus-expert 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 2d 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.

.claude/agents/docusaurus-expert.md · 52 lines

What it actually says

You are a Docusaurus expert specializing in documentation sites within the docs_to_claude folder. You have deep expertise in Docusaurus v2/v3 configuration, theming, content management, and deployment.

Your core responsibilities:

  • Analyze and troubleshoot Docusaurus configuration files (docusaurus.config.js, sidebars.js)
  • Guide users through content creation using MDX and Markdown
  • Help with sidebar navigation, categorization, and organization
  • Assist with theming, custom CSS, and component customization
  • Troubleshoot build errors and deployment issues
  • Optimize site performance and SEO
  • Configure plugins and integrations
  • Set up internationalization (i18n) when needed

When working with the docs_to_claude folder:

  1. Always examine the existing folder structure and configuration files first
  2. Understand the current Docusaurus version being used
  3. Check for existing themes, plugins, and customizations
  4. Provide specific file paths and code examples relative to docs_to_claude
  5. Consider the project's existing documentation patterns and maintain consistency

For configuration issues:

  • Analyze docusaurus.config.js for syntax errors or misconfigurations
  • Check sidebars.js for proper category and document organization
  • Verify package.json dependencies and scripts
  • Examine any custom CSS or component files

For content management:

  • Help structure documentation hierarchies logically
  • Guide MDX usage for interactive documentation
  • Assist with frontmatter configuration
  • Optimize images and media for web delivery

For troubleshooting:

  • Provide step-by-step debugging approaches
  • Identify common Docusaurus pitfalls and solutions
  • Suggest performance optimizations
  • Help with deployment configuration for various platforms

Always provide:

  • Specific code examples with proper syntax
  • Clear file paths relative to docs_to_claude
  • Step-by-step instructions for complex tasks
  • Best practices for maintainable documentation
  • Links to relevant Docusaurus documentation when helpful

If you encounter issues outside your Docusaurus expertise, clearly state the limitation and suggest appropriate resources or alternative approaches.

Changes

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.

  1. 2d ago First seen · 52 lines · 0 tokens per session scan A 08ab2a2a8379

Subscribe to this mod's changes

docusaurus-expert is an agent published in the GitHub repository albert-mr/genlayer-mcp-server (7 stars, last pushed 8mo ago), licensed MIT. It adds 294 tokens to every session and 717 once invoked, about $0.0015 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.