17,399 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.
Architecture, code review, prompting, and decision-making skills tuned to Alon Baron's engineering style: model-first, failure-path-aware, YAGNI. v2: skills self-invoke when the task shape matches. v2.1: triggers name the situation and settle overlaps with Claude Code's built-ins.
★not rated 13▲
+1 1mo agoA
tokens not measured
originalMIT
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
Audit code against NASA JPL's Power of Ten rules, extended for AI-assisted development. Use when checking code for dangerous complexity, unsafe control flow, resource leaks, hidden side effects, missing validation, weak CI gates, AI-generated artifacts, or missing failure-mode tests.
Teaches an AI agent to use grafel MCP tools as a structural second pair of eyes during code review. Covers impact radius analysis, orphan detection, dead-end flow discovery, cross-repo consistency checks, and pattern violation spotting — with a per-change-type tool sequence, a severity rubric, and worked examples.
Evaluate repository or project code quality and produce an evidence-based scorecard. Use when asked to review code quality, score a project, assess maintainability, inspect technical debt, evaluate architecture/readability/refactoring health/engineering practices/code smells, compare project quality, or prepare a…
Use when working in a repository that has jjj initialized (a .jj/jjj-meta directory), or when coordinating several agents on shared work — tracking problems, proposing competing solutions, critiquing them, and reaching decisions that survive history rewrites. Also use when asked to set up multi-agent collaboration…
Review this codebase against the prodcheck pre-production checklists — security, performance, scale, integrations and post-launch readiness. Use when asked to check whether a project is ready to ship, to audit an area before launch, or to work through a specific checklist. Produces evidence with file:line citations…
Reviews pull requests for security vulnerabilities, logic bugs, data loss risks, and API misuse. Runs project linters and type checkers to verify findings before commenting. Specialized for the Symbiosis codebase (Python stdlib-only Claude Code plugins).
Adversarial multi-agent code review. Your PR runs a gauntlet of up to seven concern-specialized agents, then survives deterministic verification, skeptical validation, and a blind challenge before anything reaches you. Prompt injection defense and flexible delivery (PR/MR comments, markdown, chat). Supports GitHub and.
★not rated 12
changed todayA
tokens not measured
originalApache-2.0
Deterministic code-graph MCP server: structural navigation, semantic find, impact analysis, and architecture decision records for the current repo. Zero infrastructure — the graph lives in .reposkein/ and the indexer binary is fetched on first run.
★not rated 12
changed 5d agoA
tokens not measured
originalApache-2.0
Run code, architecture, systems, or proposed changes through a panel of world-class engineering perspectives. Each panelist reads the ACTUAL source files before judging. Use this skill whenever the user asks to: review code quality, get expert opinions, assess architecture decisions, evaluate a refactor plan, critique…
Adversarial validation for all stages. Detects fabrications, identifies analytical flaws, challenges assumptions, makes approval decisions. Seeks problems rather than confirming quality. Does NOT complete deliverables or fix issues.
Radical-simplicity coding guidelines distilled from George Hotz's public philosophy. Use when writing, reviewing, refactoring, or porting code — to remove before adding, collapse duplication, keep interfaces narrow, and look at what code actually does instead of assuming.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
MCP server "unified-diff-mcp" as configured in gorosun/unified-diff-mcp. Launched with bun /Users/username/projects/unified-diff-mcp/src/index.ts. Needs 5 environment variables to run.
★not rated 12 1y agoA
tokens not measured
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: