19,479 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Multi-phase code-quality skill — primary frame for the evaluator role in Execute, the architecture axis in Plan, and correctness/readability in Refine. Multi-axis code review with severity vocabulary. Use when acting as the evaluator assessing a generator's output, and when reviewing any change before signalling…
MCP server bridging AI assistants to OpenAI Codex CLI for code analysis and review. Runs locally from the @trishchuk/codex-mcp-tool npm package. Needs 3 environment variables to run.
★not rated 24 1mo agoA
tokens not measured
originalMIT
Adversarial, multi-agent review of an uncommitted diff: parallel specialist reviewers, then a refutation pass that tries to disprove every finding so only real, risk-scored issues survive.
SonarQube quality gate, any language, no company server needed: run SonarQube Community Build locally (Docker), read the real gate + issues, fix by rule id, re-scan and diff. A linter's green build is a pre-check, never the gate.
A lightweight development workflow plugin that takes a product requirements document, asks questions to clarify it, helps with coding, and supports code review. A product requirements document describes what a software product should do.
★not rated 24 2mo agoA
tokens not measured
originalMIT
Software quality review and design guidance for any code: naming, cohesion, coupling, duplication, function size, dependency direction, and testability. Use when someone asks to improve, review, refactor, or design code, or asks what good structure looks like here. Routes to the sub-skill matching the kind of work.
Project code-review style for this repo. Review the current branch's changes in two passes (correctness + justify-every-line), tracing any bug claim to ground before reporting.
Several models on the same question at once — Claude sub-agents, OpenAI Codex and a cheap third via OpenCode. Review code (code-review), check whether the work is actually finished rather than finished-looking (check-if-done), brainstorm wide with a different model per cognitive frame (adhd), just ask all of them.
★not rated 24
changed 3d agoA
tokens not measured
originalMIT
A read-only code reviewer for TypeScript, TSX, React, and Next.js projects. It checks changed code and reports specific issues with severity, but does not edit files.
Scans source code for security vulnerabilities — injection flaws, authentication bypasses, hardcoded secrets, XSS, and more — then filters false positives and ranks findings by severity and confidence. Supports all programming languages. Uses a three-phase audit-filter-report workflow with customizable scan categories…
Loop Review is a periodic quality audit of the KitchenLoop's recent output. It reads experience reports, inspects merged PRs and their code changes, optionally runs external auditors (Codex, Gemini), and produces a durable synthesis report with findings categorized by severity.
A review and scaffolding guide for agent skills, including Claude and Cursor skills. It checks their instructions, descriptions, workflows, scripts, parameters, references, and delivery checklists, and can generate a skill template.
Analyze Ruby gem dependencies, vulnerabilities, outdated packages, maintenance health, and insecure gem sources with the gemtracker CLI. Use when asked to audit Ruby gems, check Gemfile.lock security, review dependency health, or run gemtracker.
A command for checking the current code for patterns described as AI slop, meaning low-quality, repetitive, or unsuitable code associated with careless AI generation.
Reviews YUP audio plugin code for YUP-specific correctness issues: AudioProcessor lifecycle, AudioParameterBuilder and AudioParameterHandle usage, editor gestures, AudioBusLayout handling, CLAP/VST3 wrapper contracts, state recall, and MIDI safety. Use when the user asks to review a YUP plugin, check a processBlock…
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: