Security & Testing Agent Skills for Claude Code

A skill with invalid characters in the name.

Use when packaging an ISSTA tool, benchmark, and results for the artifact-evaluation track, covering the ACM badges (Artifacts Available…

Use when designing or auditing ISSTA experiments, covering real subject programs and benchmarks like Defects4J, fair tool-baseline…

Use when strengthening ISSTA reproducibility and verifiability evidence, covering pinned subject programs and benchmark versions, random…

Use when revising an ISSTA paper for a clear testing/analysis contribution, covering the threat-model-then-technique structure, the…

When to activate: Java security, Spring Security, JWT, OAuth2, SecurityFilterChain, method security, CSRF, CORS, password encoding

Risk-focused Java test design, implementation, review, and CI planning.

Red-green-refactor loop for adding or changing behaviour.

Use when the user mentions Clawpatch/clawpatch.ai, semantic feature review, repo-wide AI audit, persistent findings, or clawpatch…

Use when checking code for vulnerabilities, linting shell scripts, scanning containers or IaC for security issues, or managing encrypted…

Evaluate Agent Skill design quality against official specifications and best practices.

12 regulatory & QM agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw.

Generates comprehensive stress test reports and performance trend charts from JMeter summary logs and run metrics.

Use when implementing any feature, fixing any bug, or changing behavior in TypeScript or Python — and whenever the user mentions TDD…

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands…

Audit JS/TS project code for signs of infection, malware, backdoors, or supply-chain attacks.

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code…

Audit code across 5 dimensions (accessibility, performance, theming, responsive, anti-patterns) with P0-P3 severity scoring.

Debug systematically using root-cause analysis.