enhance-plugins

To audit plugin structures for security and compliance gaps, you can analyze plugin directories to validate tool schemas, plugin.json configurations, and security patterns against best practices. This process identifies structural issues and potential risks while generating a comprehensive markdown report to streamline development pipeline reviews.

MCP tool schema validation checks the structure and definitions of Model Context Protocol tools within your plugins to ensure they meet best practices. It analyzes the tool schemas across plugin ecosystems to detect compliance gaps and offers auto-fix guidance for high-certainty structural issues.

Yes, the plugin audit applies to Claude Code, OpenCode, and Codex plugin ecosystems. It analyzes discovered plugins across these platforms to validate tool schemas, plugin structure design, and security controls, ensuring best practices are maintained throughout your development pipelines.

Yes, you can automatically fix high-certainty security issues discovered during a plugin audit. The analysis offers auto-fixes for HIGH-certainty issues while carefully preserving your existing configurations, ensuring that corrections do not break current plugin functionality or override custom settings.

The best way to validate plugin.json, commands, and agents layout is to run a structural analysis against your plugin directory. This checks the files against best practices, detects structural design issues, and generates a markdown report with corrective actions to streamline your review process.

The main limitation of auto-fixing plugin security patterns is that automated corrections are restricted to HIGH-certainty issues only. Lower-certainty risks are flagged in the structured report for manual review, and all existing configurations are preserved to prevent unintended modifications to your development pipeline.