17,101 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.
Plugin Claude Code
Bundles 1 skill, 4 commands · 40 tokens together
Navigate AI conversation logs like a debugger. Use when analyzing past agent sessions, understanding what happened in a conversation, building custom log readers, or extracting workflows and lessons from session data.
Skill Claude CodeCodex
Deterministic simulation testing for containerized services. Write Lua scripts to inject chaos (pause, kill, resource deprivation) into Docker containers with reproducible, seeded fault injection. Use when writing chaos experiments, testing service resilience, or debugging distributed systems.
Agent Claude Code
Build error fixer. Runs the build, parses errors, and applies minimal mechanical fixes one at a time.
Skill Claude CodeCodex
Trace the impact (blast radius) of a code change in ANY codebase and prove it didn't break anything else — language- and framework-agnostic. Use RIGHT AFTER a fix to a feature, function, module, type, route, API endpoint, schema, or config, before committing, opening a PR, or pushing. Triggers: "did this break…
Skill Codex
Reduction-first coding for every change, whether building, fixing, refactoring, or cleaning up. Delete, merge, or replace before adding, so the project ends up smaller and simpler without losing anything the app needs, in code and in the text around it. Matters most for cleanups, refactors, and larger changes.
Skill Claude CodeCodex
A template-repository issue-handling workflow for investigating reports from consumer repositories, reproducing problems, identifying root causes, and proposing fixes. After approval, it updates the shared template files and runs tests.
Plugin Claude Code
Bundles 1 skill, 4 commands, 1 hook · 56 tokens together
Structured error and success logging for agentic coding. Log what went wrong, trace it back to your input, and generate CLAUDE.md rules from patterns.
Skill Claude Code
Top-down, whole-system audit of a codebase's DEEP LOGIC - the bugs that live in the SEAMS between modules, not inside any one file. Finds contracts that drift across module boundaries, invariants enforced on one path but broken on a sibling path, cross-cutting responsibilities (deletion cascade, tenant-scope…
Command Claude Code
Solves command invocation errors through validation, helpful error messages, and guided execution.
gmen1057/claude-code-starter-kit
Skill Claude Code
Use when encountering any bug, test failure, or unexpected behavior — before proposing fixes.
pruthvinathJV/nextjs-claude-code-kit
Command Claude Code
Audit caching configuration in $ARGUMENTS for Next.js 15 correctness.
marcelopalin/claude-howto-pt-br
Skill Claude CodeCodex
Refatoração sistemática de código baseada na metodologia de Martin Fowler. Use quando usuários pedem para refatorar código, melhorar estrutura de código, reduzir dívida técnica, limpar código legado, eliminar code smells ou melhorar a manutenibilidade do código. Esta skill guia através de uma abordagem em fases com…
derjochenmeyer/claude-code-craft
Skill Claude Code
Fast project health check. Structure completeness, namespace purity, file staleness, hook functionality, decisions format, memory adoption, dream history, setup quality — all from local files. Works with or without git. No agents, no external fetches, 15-30 seconds. For deep analysis with feature adoption and session…
Skill Claude Code
Structured debugging assistant. Use /debug to get a guided diagnosis of any bug — Claude will ask the right questions and then pinpoint the root cause.
Skill Claude CodeCodex
Static call-path engine. Answers "what calls what?" from structure, not execution. Use before reading source files — it is faster and token-cheaper than grep-and-read.
Cursor rule Cursor
Use when a shell command unexpectedly changed or deleted files, when you need to find which command touched a file, or to roll files back to before some command — bashback snapshots every command's file side effects and can undo them.
Skill Claude Code
Systematic debugging skill for root-cause/fix of concrete bugs and failing tests. Use for debug, investigate, resolve, fix, root-cause, wrong behavior, flaky/CI/prod-only failure, runtime/build error, or performance anomaly. Use sdcorejs-test for write/run/plan tests without fix intent. Runtime-localized.
MCP server Claude CodeCodexCursor +2
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
Cursor rule Cursor
Defensive coding — type safety, null checks, and input validation.
Skill Claude CodeCodex
A backend API investigation skill that maps interfaces, traces individual request paths, and diagnoses server errors. It applies to common frameworks such as Spring, Express, FastAPI, and Gin.
MCP server Claude CodeCodexCursor +2
MCP server "onlinegdb-cpp-executor" as configured in ayushtiwari110/gdb-MCP-Server. Needs 2 environment variables to run.
Skill Claude Code
Explore and understand code structure efficiently using semantic navigation. Use when exploring unfamiliar code, understanding architecture, finding symbol relationships, or investigating how something works.
Skill Claude CodeCodex
Structured human-in-the-loop debugging mode for when static code reading isn't enough. Use this skill whenever you're stuck debugging an issue where you can't tell what's actually happening at runtime — async timing, complex control flow, multiple call paths, conditional branches, or bugs that only reproduce when the…
SuperMalow/personal-agent-skills
Skill Claude CodeCodex
Read-only root-cause diagnosis for bugs, failures, flaky behavior, and performance regressions. Use when the user asks to diagnose, investigate, debug, explain, or find the cause of broken, throwing, failing, incorrect, intermittent, or slow behavior. Gather evidence and report the likely root cause without modifying…
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: