Audit, manage, and troubleshoot the entire Claude Code ecosystem — skills, agents, hooks, plugins, MCP servers, LSP configs, memory files, settings, and output styles — with automated quality checks, documentation delegation, performance diagnostics, and social feed monitoring.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
PROACTIVELY use when creating, reviewing, or validating Claude Code subagents. Audits for quality, compliance, and maintainability - checks YAML frontmatter, name/description requirements, tool access, model selection, color, and permissions configuration. Used by /audit-agents for parallel auditing.
PROACTIVELY use when analyzing agents for consolidation opportunities. Compares agent configurations, identifies shared patterns, tracks component references, and assesses consolidation impact. Used by /audit-agent-consolidation for parallel analysis.
PROACTIVELY use to validate audit findings before presenting results. Cross-references findings against official docs, MCP servers, and development skills to filter false positives. Spawned by audit commands when validation is enabled (default).
PROACTIVELY use when troubleshooting Claude Code errors, checking for known issues, or finding workarounds. Searches anthropics/claude-code GitHub issues automatically. Use for error investigation, duplicate checking, and workaround discovery.
PROACTIVELY use when reviewing skills or memory files for docs-management delegation compliance. Detects hardcoded Claude Code data and verifies proper delegation patterns. Used by /audit-docs-delegation for parallel auditing.
Central authority for Claude Agent SDK (TypeScript and Python SDKs). Covers SDK installation, authentication (Anthropic key, Bedrock, Vertex), sessions and resumption, forking sessions, streaming vs single mode, custom tools, permissions (allowedTools, disallowedTools, permissionMode), MCP integration, system prompts (CLAUDE.md, appendSystemPrompt, outputStyle), cost tracking, todo tracking, structured outputs, hosting patterns, plugins, and SDK branding guidelines. Assists with building custom agents, configuring SDK options, and troubleshooting SDK issues. Delegates 100% to docs-management skill for official documentation.
Analyze agents for consolidation opportunities. Groups agents by configuration, tracks references, and manages refactoring.
Audit Claude Code subagents for quality, compliance, and maintainability. Use after creating or modifying agents, before releases, or for periodic quality checks.
Audit skills and memory files for docs-management delegation compliance. Detects hardcoded Claude Code data and verifies proper delegation patterns.
Audit Claude Code hooks for quality, compliance, and maintainability. Use after creating hooks, before releases, or for periodic quality checks.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Plugins for Claude Code: documentation management, code quality, and ecosystem support.
fnm (Fast Node Manager) is the recommended Node.js version manager for this project. It:
Install fnm:
# Windows (PowerShell as Admin)
winget install Schniz.fnm
# macOS/Linux
curl -fsSL https://fnm.vercel.app/install | bash
Configure for Git Bash (add to ~/.bashrc):
eval "$(fnm env --use-on-cd --shell bash)"
Or source the setup script which includes fnm initialization:
source "/path/to/claude-code-plugins/setup/bashrc-claude.sh"
Install Node:
fnm install 24
fnm default 24
npm install
npm run lint:md # Check for errors
npm run lint:md:fix # Auto-fix errors
Markdown linting runs automatically on PRs via GitHub Actions. The same rules apply locally and in CI.
/plugin install claude-ecosystem@claude-code-plugins
/plugin install code-quality@claude-code-plugins
/plugin install google-ecosystem@claude-code-plugins
This repo expects Codex CLI configuration to live in user scope under ~/.codex.
See .codex/README.md for the canonical locations.
| Plugin | Purpose |
|---|---|
| atlassian | Atlassian MCP server: Jira, Confluence, Compass integration |
| browser-automation | Browser automation MCP servers: Chrome DevTools, Playwright |
| business-analysis | BABOK techniques: capability mapping, stakeholder analysis, value streams, journey mapping |
| ci-cd | CI/CD pipelines: GitHub Actions, deployment automation, release management |
| claude-code-observability | Event logging, metrics, session diagnostics |
| claude-ecosystem | Claude Code docs, meta-skills, hooks, observability, auditors |
| code-quality | Code review, markdown linting, debugging, CI/CD templates |
| compliance-planning | Regulatory compliance: GDPR, HIPAA, PCI-DSS, AI governance, ISO 27001 |
| content-management-system | Headless CMS architecture: content modeling, taxonomies, media, theming |
| cursor-ecosystem | Cursor IDE docs, CLI, agent, keyword-based search |
| documentation-standards | Technical docs: arc42, C4 model, ADRs, RFC process, docs-as-code |
| dotnet | .NET 10+ automation: build, clean, SDK/tool install, version upgrades, Aspire MCP |
| duende-ecosystem | Duende IdentityServer, BFF, IdentityModel docs |
| enterprise-architecture | TOGAF, Zachman, ADRs, cloud alignment |
| event-modeling | Event-driven design: Event Modeling, Event Storming, CQRS, sagas |
| figma | Figma MCP server: design context, code generation, design tokens |
| formal-specification | Formal methods: UML/SysML, TLA+, OpenAPI/AsyncAPI, state machines |
| git | Git config, GPG signing, hooks, GitHub issues, history exploration |
| google-ecosystem | Gemini CLI docs, Claude-to-Gemini integration, configuration management |
| melodic-software | Developer onboarding, environment setup, commit workflows |
| microsoft | Microsoft MCP servers: Microsoft Learn, Azure, NuGet, Azure DevOps |
| milan-jovanovic | Milan Jovanovic .NET patterns: Clean Architecture, DDD, CQRS, EF Core |
| openai-ecosystem | OpenAI Codex CLI docs |
| requirements-elicitation | Requirements gathering: LLMREI interviews, gap analysis, prioritization |
| research | Research workflows: MCP integration, multi-source synthesis, structured output |
| response-quality | Response quality standards, source citations |
| security | Security: OWASP, authentication, cryptography, DevSecOps, threat modeling, 12 skills |
| soft-skills | Career progression, interviews, communication, professional visibility |
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub melodic-software/claude-code-plugins --plugin claude-ecosystemComprehensive security plugin: OWASP Top 10, authentication patterns, cryptography, API security, secrets management, supply chain security, DevSecOps, container security, zero trust, and threat modeling.
melodic-softwareDiagrams-as-code tools for visualizing code, data, and systems using Mermaid and PlantUML
melodic-softwareOpenAI Codex CLI ecosystem plugin with documentation management, scraping, indexing, and search capabilities
melodic-softwareMilan Jovanovic .NET patterns plugin: blog content management, article discovery, and proactive project analysis for Clean Architecture, DDD, CQRS, EF Core, and ASP.NET Core patterns
melodic-softwareTactical Agentic Coding course content by @IndyDevDan - Master agentic coding tactics to scale engineering and build self-operating codebases
melodic-softwareTactical Agentic Coding course content by @IndyDevDan - Master agentic coding tactics to scale engineering and build self-operating codebases
melodic-softwareClaude Code workflow patterns: prompting, CLAUDE.md maintenance, multi-agent orchestration
spences10Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: <example>Context: The user has just implemented a new authentication service and wants to document it properly. user: 'I just finished implementing the auth service, can you document how it works?' assistant: 'I'll use the codebase-documenter agent to analyze the authentication service and create detailed documentation in CLAUDE.md' <commentary>Since the user has completed a service implementation and needs documentation, use the Task tool to launch the codebase-documenter agent to create comprehensive CLAUDE.md documentation.</commentary></example> <example>Context: The user wants to ensure a newly added API module is properly documented for the team. user: 'We need documentation for the new payment processing API I just added' assistant: 'Let me use the codebase-documenter agent to analyze the payment processing API and create proper documentation' <commentary>The user needs documentation for a new API module, so use the codebase-documenter agent to create CLAUDE.md files with setup instructions and architectural notes.</commentary></example>
ananddtyagiAudit and optimize Claude Code configurations with dynamic best-practice research
acostanzoAnalyze codebases and recommend tailored Claude Code automations such as hooks, skills, MCP servers, and subagents.
anthropicsPrompt engineering techniques for accurate, grounded Claude responses — anti-hallucination workflow with citation-backed analysis
laurigates