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.
Strict multi-agent Supervisor for Claude Code: web-grounded anti-hallucination, expert coding/frontend implementation, independent judges, adversarial review, and final Stop release gate.
Useful AI things an engineer uses daily. Ships prodcheck (senior-engineer production review), prodtest (senior-QA test pass with Playwright), mergemain (context-aware merge of main into the current branch), shipit (clean commits and PRs, with or without AI attribution), and adonis-next-monorepo (scaffolds a verified…
★not rated 4
changed 11d agoA
tokens not measured
originalMIT
Evidence-first codebase audit for correctness, security, privacy, data, integration, operational, test, and docs-vs-reality risks. Use when the user asks for a Fable-5 audit, exhaustive audit, bug hunt, risk review, codebase audit, security/integration audit, or asks Codex to find issues before changing code.
Manage resident peer agents: long-running monitors that live inside the pi session, tick on minute intervals, watch the main agent's work, and push findings back mid-turn. Use when the user asks to launch/stop/ask a peer, watcher, monitor, observer, sentinel, or auditor; wants standing review, drift/scope watching…
Create or check concise reviewer-visible PR context and practical proof when an authorized workflow publishes an update or prepares it for merge. Lead with what broke and how it is fixed, use actual product screenshots for static UI changes and recordings for motion or manual interaction, keep technical diagrams as…
The house Rails style, distilled from 37signals practice (Campfire, Fizzy, DHH's reviews). Use for all Rails coding, refactoring, and code review so architecture, naming, and safety standards stay consistent; fires on work touching models, concerns, controllers, routing, REST, authorization, dependencies, naming…
Stack-agnostic coding agents and orchestrator skills for feature planning, PR review, design review, PR batching, issue triage, simplification, codebase mapping, installing the agents on a periodic schedule, and a manager console that delegates work items to worker agents.
Use when reviewing production readiness, resilience, failure modes, or reliability of code, services, or system designs. Trigger for requests about error handling, retries, timeouts, circuit breakers, graceful degradation, observability, DR/RPO/RTO, abuse resilience, quota exhaustion, production architecture…
Deep code review with 23+ specialist Opus agents. Full call-graph tracing, web-verified findings, adversarial false-positive filtering. Supports GitHub PRs, GitLab MRs, and local branch comparisons.
★not rated 4 6mo agoA
tokens not measured
originalMIT
MCP server "mcp-devils-advocate" as configured in AleBrito124356/mcp-devils-advocate. Runs locally from the mcp-devils-advocate Python package. Needs 1 environment variable to run.
★not rated 4 1mo agoA
tokens not measured
originalMIT
Matt Pocock's agent skills for real engineering: grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.
★not rated 4
changed 1mo agoA
tokens not measured
originalMIT
An Epic Story Review runner is a coordinator for reviewing all Stories in an Epic, where an Epic is a large body of related development work. It runs review, evaluation, and fixes one after another, then makes a local commit when requested.
Review a skill bundle, a prompt-like file (AGENTS.md, a guideline, an agent definition), or a change to them for conflicts, text past its allowance, and dropped parsed contracts, returning findings, a branch ledger, and a ship-ready verdict; --fix rewrites from the ledger. Trigger on 'review this skill change', 'is…
★not rated 4 yesterdayA84 tokens
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: