Security & Testing Agent Skills for Codex CLI

Agent skill for v3-security-architect - invoke with $agent-v3-security-architect

Complete security architecture overhaul for claude-flow v3.

Single-task completion verifier. When an implementer claims a task or feature is finished, establish whether the goal was genuinely…

This skill enables Claude to validate Cross-Origin Resource Sharing (CORS) policies.

Validate CSRF protection implementations for security gaps.

Find similar vulnerabilities and bugs across codebases using pattern-based analysis.

Mutation-driven test vector generation. Finds implementations of a cryptographic algorithm or protocol, runs mutation testing to identify…

Apply Vercel security best practices for secrets, headers, and access

Fast, precise unit test runner — enforces TDD (RED-GREEN-REFACTOR), runs test suites with coverage, generates test scaffolding, and…

This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating…

Verify an Obsidian plugin with Node unit tests, typecheck, production build, and Selenium E2E against real Obsidian.

SeldonFrame merge gate — run unit tests + tsc + check-use-server + migration-journal + regression-grep and return ONE pass/fail verdict.

Prove a change actually works before it counts as done.

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session…

Generate a project-local verification skill that drives the app the way a user does — any language, framework, or platform.

Concrete, per-area proof that a change actually works before reporting it fixed, done, or "should work now" — which dev server, test…

Use when about to run tests/builds for ctsnetwork-event, after editing any file in event/backend or event/frontend, or before reporting…

Verify the Omnigent CLI's setup/onboarding flow, terminal UI/UX, and critical user journeys in a completely isolated, reproducible loop.

Use when applying web best practices — security headers, modern APIs, error handling.

Use when stakes are high — adversarial fresh-context review of every non-trivial decision.

Use when handling user input, auth, secrets, or external integrations — prevent OWASP Top 10, enforce auth patterns, secrets management…