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/Justdvp/claude-code-templatesWrote 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/justdvp/claude-code-templates/docusaurus-expert)<a href="https://agentmods.dev/agents/justdvp/claude-code-templates/docusaurus-expert"><img src="https://agentmods.dev/badge/agents/justdvp/claude-code-templates/docusaurus-expert/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/justdvp/claude-code-templates/docusaurus-expert"><img src="https://agentmods.dev/badge/agents/justdvp/claude-code-templates/docusaurus-expert.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.00049 | $0.01023 |
| Opus 5.5 | $0.00020 | $0.00409 |
| Sonnet 5.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 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 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.
- 1mo ago First seen · 174 lines · 49 tokens per session scan A 4c8150093856
docusaurus-expert is an agent published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 8d ago), licensed MIT. It adds 49 tokens to every session and 1,023 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 docusaurus-expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
adp-reviewer-high
High-effort reviewer for risky, security-sensitive, or repeatedly failing work. Fresh-context, read-only by instruction. Checks the approved contract, the actual diff, and validation evidence; leads with defects.
adp-worker-high
Escalation sole writer (high effort) for an approved Controlled contract. Implements only the contract's owned files and returns the diff and validation output.
adp-explorer
Read-only explorer for locating code, conventions, and facts. Returns findings, never edits.
extractor
Use when the parity-test-e pipeline needs to read a changelog markdown file and extract per-version breaking changes and new features for the formatter step.
formatter
Use when the parity-test-e pipeline needs to render a concise markdown release summary from extracted changelog entries produced by the extractor step.
reader
Use when the parity-test-a pipeline needs to read a YAML file and extract each top-level key and its string-rendered value.