Skip to content

lidge-jun/codexclaw / plugins/codexclaw/skills/dev-security

cxc-dev-security

Unverified

Use for security and trust boundaries. Triggers: auth, secrets, XSS, CSRF, SQL injection, JWT, OAuth, OWASP, PII, uploads, payments, supply chain, CI integrity, agent security, threat model.

Dev-Security — Production Security Hardening

Treat security as a build constraint, not a cleanup step. This skill is the authoritative source for authentication, authorization, input validation, secrets, headers, rate limiting, supply-chain security policy and evidence requirements, PII handling, and agentic AI safety. Validation ownership split: this skill owns what the validation schema enforces (content/policy); placement (boundary-only validation) is owned by dev-architecture §4. dev-backend delegates here for policy and verification depth. dev-frontend remains responsible for UI implementation, but frontend security touchpoints such as CSP compliance, CORS behavior, XSS prevention, and dependency auditing are defined here. This skill activates by change-surface whenever code crosses a trust boundary or changes the blast radius of a failure.

Before security work, read dev for classification, fast paths, rule authority, family invariants, verification, and safety; current CVEs/public evidence follow its Conditional Routes.

Threat Model First

Rule (SEC-THREAT-01): Security-sensitive changes start with a repo-grounded threat model, then controls. Do not begin with a checklist and assume it is sufficient.

Before implementation, read the threat-model procedure; before completion, read the applicable security review and must-pass addenda.

Modular References

ConditionReference
Before security-sensitive implementationThreat model
Input validation, login/session/token/OAuth, authorization, or sensitive flowsAccess controls
Secrets, headers/CSP/CORS, or abuse/rate limitsRuntime controls
AI-suggested dependencies, security claims/static checks, agent configuration, MCP, or sandboxingAgent integrity and scans (SEC-ANTIPATTERN-01)
Security-sensitive completion, deploy/release, uploads/payments/logging/PII, or control ownershipSecurity review and ownership matrix, ASVS checklist
Any security-sensitive codeOWASP Top 10
JS/TS, Python, SQL, or Go security workLanguage quirks
Before claiming code is secureStatic analysis recipes
Tool-using agents or prompt-driven flowsAgentic AI
LLMs, RAG, or tool/agent outputLLM supply chain
Add/vet MCP serversMCP supply chain
Dependency audit or release integritySBOM and signing
Domain implementation, CI credential delivery/signing, frontend, testing, review, RCA, scaffolding, or pipelinesCompanion owners; load the domain skill too

Read only the references relevant to the current task. A small CSS change needs no OWASP reference. Auth, data access, secrets, file uploads, webhooks, or incident response changes do.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 192kUpdated Claude CodeCodexVerifiedInstall