15,552 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.
Hypothesis-driven problem solving for AI agents: probe, falsify, escalate — never blind-retry. Bundles the behavioral skill and the inquisitor-mcp server (web search, project analysis, code tracing, phase tracking).
★not rated 5 1mo agoA
tokens not measured
originalMIT
Debug and diagnose Kubernetes clusters using KubeView MCP server tools. Use when investigating cluster issues (pod crashes, deployment failures, service connectivity problems, node issues, resource constraints), performing cluster health checks, or troubleshooting any Kubernetes workload. Trigger phrases include…
Generate and incrementally maintain an interactive architecture map plus a per-module code-quality audit (health scores 0-100, smell findings, lines-of-code, and a clickable dependency graph) for any codebase. Use when the user wants to visualize a project's functional modules, audit or score code quality, check…
Diagnose and repair Claude Desktop Mac third-party inference / 3p / DeepSeek-style Claude Code setups for best-effort parity with first-party Claude Code. Use when users mention Claude Code Mac app developer mode, Claude Desktop 3p, third-party API providers, DeepSeek V4 Pro/Flash, bypassPermissions not working…
This skill should be used whenever implementation or review depends on external, version-sensitive facts: libraries, SDKs, APIs, CLIs, cloud services, security advisories, changelogs, release notes, or documentation that may have changed. The skill anchors local versions, ranks source quality, runs an executable probe…
A step-by-step debugging guide based on reproducing a failure, testing one explanation at a time, making the smallest relevant change, and checking the result. It includes a stopping rule for repeated unsuccessful fixes.
Use when the user works in their own codebase with Zephex MCP or the zephex terminal CLI: onboard a repo, find or read code, map architecture, run or diagnose tests, check packages before install, audit a live HTTPS URL, remember project facts, or debug multi-file issues — including when they only say "use Zephex,"…
Use when hunting the cause of a bug, error, or failing test — and before proposing any fix. Triggers - "why doesn't this work", stack traces, flaky failures, regressions ("worked yesterday"). Output is reproduce → root cause → minimal fix → regression test. If you already know the cause and just need the fix, use…
Drive IDA Pro through the IDA Pro MCP like a senior reverse engineer: don't just narrate decompiler output, transform the database. Use this whenever the user is reverse engineering, analyzing malware, working a crackme or CTF, or doing binary/firmware analysis with IDA Pro over an MCP connection (mrexodia/ida-pro-mcp…
A codebase scan for five common weaknesses in the setup used to guide and check an AI agent. It produces a diagnostic report and can optionally fix the problems it finds.
Diagnose and carry out the migration of an MCP server to the 2026-07-28 specification. Runs a deterministic rule engine over the code, then walks the remediation per finding: stateless transport, OAuth 2.1, the deprecated capabilities, and the SDK v2 rename.
★not rated 5
changed 4d agoA
tokens not measured
originalMIT
Aggregate breadcrumbs, escalations, and audit logs from the last 14–30 days to surface recurring correction patterns that should be fixed at the source level (brief template, config/, WORKER-RULES.md) rather than re-fixed each session. Use during weekly maintenance Phase 2, after a redo dispatch, or when the operator…
Tight cause-fix-test triage from a pasted error or stack trace. No lectures, no bullet-point philosophy -- just cause, fix, regression test, sibling files to update.
★not rated 5 3d agoA
tokens not measured
originalMIT
A multi-role code-review process that searches for problems, tries to disprove the proposed changes, and reproduces issues in a sandbox. Different agents or backends can take part in the review.
Search, submit, and vote on coding solutions via the AgentInSync collaborative knowledge base. Use when encountering errors, stack traces, bugs, crashes, exceptions, "not working" issues, or after fixing a non-trivial bug. Also activates for "how to" questions about debugging workflows.
Investigate Linux package, build, command, vulnerability, distribution migration, ELF/ABI, shared-library, and container issues with distro-aware PkgSeek evidence. Use for apt, apt-get, dpkg, yum, dnf, rpm, apk or pacman errors; missing commands, headers and .so files; CVE/CNNVD and backport checks; Debian, Ubuntu…
Real-time metacognition for Claude Code. Six senses detect stuck loops, validation bias, repeated errors, and circular actions. Learns what works across sessions.
★not rated 5 4mo agoA
tokens not measured
originalApache-2.0
Use this skill when the user is debugging a bug, error, crash, or issue that might be tied to a specific point in time (e.g., "crash from 3 hours ago", "bug in v2.4.1", "last night's deploy"). It guides the agent to reconstruct the historical code state and analyze the bug in that context.
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search.
Use when debugging or changing behavior based on an uncertain causal hypothesis that the next action can test.
★not rated 5 1mo agoA23 tokens
originalMIT
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: