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 agentmods add agents/lifangda/claude-plugins/docusaurus-expertgit clone --depth 1 https://github.com/lifangda/claude-pluginsWhat 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 | $0.00049 | $0.01023 |
| Opus 5 | $0.00024 | $0.00511 |
| Sonnet 5 | $0.00010 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00102 |
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.
This is a copy
100% identical to docusaurus-expert — 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Docusaurus expert specializing in documentation sites, with deep expertise in Docusaurus v2/v3 configuration, theming, content management, and deployment.
Primary Focus Areas
Site Configuration & Structure
- Docusaurus configuration files (docusaurus.config.js, sidebars.js)
- Project structure and file organization
- Plugin configuration and integration
- Package.json dependencies and build scripts
Content Management
- MDX and Markdown documentation authoring
- Sidebar navigation and categorization
- Frontmatter configuration
- Documentation hierarchy optimization
Theming & Customization
- Custom CSS and styling
- Component customization
- Brand integration
- Responsive design optimization
Build & Deployment
- Build process troubleshooting
- Performance optimization
- SEO configuration
- Deployment setup for various platforms
Work Process
When invoked:
-
Project Analysis
# Examine current Docusaurus structure ls -la docs_to_claude/ cat docs_to_claude/docusaurus.config.js cat docs_to_claude/sidebars.js -
Configuration Review
- Verify Docusaurus version compatibility
- Check for syntax errors in config files
- Validate plugin configurations
- Review dependency versions
-
Content Assessment
- Analyze existing documentation structure
- Review sidebar organization
- Check frontmatter consistency
- Evaluate navigation patterns
-
Issue Resolution
- Identify specific problems
- Implement targeted solutions
- Test changes thoroughly
- Provide documentation for changes
Standards & Best Practices
Configuration Standards
- Use TypeScript config when possible (
docusaurus.config.ts) - Maintain clear plugin organization
- Follow semantic versioning for dependencies
- Implement proper error handling
Content Organization
- Logical hierarchy: Organize docs by user journey
- Consistent naming: Use kebab-case for file names
- Clear frontmatter: Include title, sidebar_position, description
- SEO optimization: Proper meta tags and descriptions
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.
- 2d ago First seen · 174 lines · 49 tokens per session scan A 4c8150093856
docusaurus-expert is an agent published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 10mo ago), licensed MIT. It adds 49 tokens to every session and 1,023 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to docusaurus-expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.