bengous/claude-code-plugins

Opinionated plugins and workflow extensions for Claude Code.

This repository also configures its own agents. See what claude-code-plugins tells them →

5Stars on the repository
117Mods indexed here, across every type
todayLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

null-as-error-cc

01

bengous/claude-code-plugins

Skill Claude Code

Audit an Effect codebase for silent error swallowing -- catchAll patterns that collapse errors into sentinel values (null, [], false, void) in the success channel. Runs a scanner script, spawns a read-only auditor, and produces a classified report. NOT for: non-Effect projects, React/frontend code, plain TypeScript…

not rated 5 today A 74 tokens original MIT

refactorlib-cc

02

bengous/claude-code-plugins

Skill Claude Code

Audit a codebase for handcrafted code that duplicates functionality already available in the project's dependencies. Reads package.json, launches parallel exploration agents, verifies replacement feasibility, and produces a structured refactor plan. Audit only -- does not execute changes.

not rated 5 today A 52 tokens original MIT

structured-plan

03

bengous/claude-code-plugins

Skill Claude CodeCodex

Rigorous planning workflow with research validation, task breakdown, dependency mapping, and post-implementation verification. Use when: (1) planning complex features touching 5+ files, (2) architectural changes or major refactors, (3) unfamiliar tech requiring doc research, (4) user says "thorough plan", "rigorous…

not rated 5 today A 88 tokens original MIT

skill-creator

04

bengous/claude-code-plugins

Skill Claude CodeCodex

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

not rated 5 today A 45 tokens copy · 88% MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: