Agent
A security-review guide for finding and fixing common web application vulnerabilities, including exposed secrets, unsafe input handling, broken access control, and risky dependencies.
Agent
A security-review guide for finding and fixing common web application vulnerabilities, including exposed secrets, unsafe input handling, broken access control, and risky dependencies.
Agent
A test-driven development guide, where tests are written before the code they check.
Command
An automatic command selector that reads a described task and routes it to a matching development command.
Command
A command that incrementally fixes TypeScript and build errors by running the project build, grouping and explaining errors, applying fixes, and checking the result again.
Command
A review command that examines uncommitted code changes for security problems, code-quality issues, and common development mistakes.
Command
A command that uses Playwright to create and run end-to-end tests, which check complete user journeys through an application.
Command
A planning command that restates a development request, identifies risks, and creates a step-by-step implementation plan. It waits for the user's approval before code changes begin.
Command
A dead-code cleanup command for finding code that is no longer used and preparing safe removals. Dead code means files, exports, or dependencies that the project does not use.
Command
A command that uses test-driven development (TDD): define the code interface, write tests first, implement the smallest working solution, and then improve it. It also checks that at least 80% of the code is covered by tests.
Command
A command that checks automated-test coverage and creates tests for code paths that are not tested. Test coverage measures which parts of a program are exercised by tests.
Command
A command that scans a codebase and updates concise architecture documents describing its backend, frontend, data model, and overall structure.
Command
A command that creates developer documentation from project settings and environment examples. It uses package.json, a file that defines project scripts, and .env.example, a template listing configuration variables.
Hook
One of 3 in hooks.json
Runs before the agent uses a tool for tool == "Bash" && tool_input.command matches "(npm run dev, pnpm( run)? dev, yarn dev, bun run dev)", tool == "Bash" && tool_input.command matches "(npm (install, test), pnpm (install, test), yarn (install, test), bun (install, test), cargo build, make, docker, pytest, vitest…
Hook
One of 3 in hooks.json
Runs after a tool call finishes for tool == "Bash", tool == "Edit" && tool_input.file_path matches "\\.(ts, tsx, js, jsx)$", tool == "Edit" && tool_input.file_path matches "\\.(ts, tsx)$", tool == "Edit" && tool_input.file_path matches "\\.(ts, tsx, js and jsx)$" tool calls, running #!/bin/bash (4 commands). From…
Hook
One of 3 in hooks.json
Runs when the agent finishes a response, running #!/bin/bash. From zhukunpenglinyutong/ai-max.
Skill Claude CodeCodex
A security checklist for code that handles login permissions, user input, uploaded files, passwords, API keys, payments, or other sensitive data.
Skill Claude CodeCodex
A test-driven development workflow, meaning tests are written before the code, with unit, integration, and browser-based end-to-end tests.
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: