20,069 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.
A guide for documenting and testing an existing software feature or page by studying how its code already works. It creates requirement, design, and test documents that describe the current behavior rather than an imagined future version.
Writes unit and integration tests for new or modified code. Use this agent when the user asks to add test coverage, test-drive a feature, or when a PR lacks tests.
Command "matchers" from romilly/claude-code-helpers, covering pyhamcrest custom matchers guide, when to create a custom matcher, spotting opportunities, before - verbose and redundant length check and after - expressive, no length check needed.
Benchmark whether Atlas measurably improves coding-agent behavior, by running every scenario twice — with and without Atlas — in clean contexts and scoring the pair blind.
An independent check of code written by a code executor against success criteria defined by a task decomposer. It runs test commands and produces a structured pass-or-fail report, but does not write or repair code.
Cursor rule "development-workflow" from kurisu-dotto-komu/next-agentic-coding, covering development workflow standards, development server, git operations, documentation creation and testing and linting commands.
Design, red-team, ship and debug hard Terminal-Bench 2 / Harbor benchmark tasks: the measured laws for what makes agents actually fail, the kill-list of dead task shapes, and how to clear all 17 review stages in one push instead of three. Use for benchmark task slots, TB2/Harbor tasks, task.toml, instruction.md, task…
SAGE — spec-first, AI-assisted development workflow using SDD, BDD, and Harness Engineering. Use this skill whenever the user types /sage, wants to write a spec, generate behavior scenarios, generate code from a spec, export a PR description or documentation, manage a project harness, or mentions spec.md, behavior.md…
Browser-based QA: exercises the running app via Playwright MCP, captures console errors and visual evidence, optionally fixes source bugs with atomic commits and generates regression tests. Three tiers (quick / standard / exhaustive). Writes uv-out/qa-state.md so /uvs-commit and /ship can detect completion and read…
A local development check for the Mentora application, which runs across API, web, and desktop parts. It starts the project on a Windows computer and verifies that the parts work together.
A set of practices for running Java backend integration tests with Maven, Spring Boot, Testcontainers, Docker Desktop, and MySQL containers. It covers container resource issues, Spring Boot null-safety rules, and changes to shared test base classes.
Use when writing or modifying Scala 3 tests with weaver-cats, weaver-discipline, or weaver-scalacheck; covers suites, effects, expectations, resources, and laws.
★not rated 2 3mo agoA43 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: