lidge-jun/codexclaw / plugins/codexclaw/skills/dev-security
cxc-dev-security
FlaggedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.0 KB |
| agents/openai.yaml | config | 158 B |
| references/01-threat-model.md | markdown | 1.3 KB |
| references/02-access-controls.md | markdown | 3.3 KB |
| references/03-runtime-controls.md | markdown | 3.6 KB |
| references/04-agent-integrity.md | markdown | 3.3 KB |
| references/05-security-review.md | markdown | 4.9 KB |
| references/agent-skill-integrity.md | markdown | 2.2 KB |
| references/agentic-ai-security.md | markdown | 6.0 KB |
| references/asvs-checklist.md | markdown | 3.1 KB |
| references/language-quirks.md | markdown | 5.0 KB |
| references/llm-supply-chain.md | markdown | 7.4 KB |
| references/mcp-supply-chain.md | markdown | 6.9 KB |
| references/owasp-top10.md | markdown | 11.1 KB |
| references/static-analysis.md | markdown | 4.8 KB |
| references/supply-chain-sbom.md | markdown | 6.7 KB |
references/asvs-checklist.md
View on GitHub# Application security release checklist — ASVS-informed, not a conformance certificate
This is a local risk checklist, not the complete OWASP ASVS and not an official L1/L2
mapping. Keep existing assurance requirements: the local baseline target is L1 for
ordinary authenticated apps and L2 for admin, multi-tenant, PII, payments, uploads,
and elevated internal tools. The threat model may require more; lowering an existing
target requires a separately approved policy, not this documentation rewrite.
Passing these summaries alone does not establish ASVS compliance.
## Official baseline
For formal assessment, pin the official [ASVS 5.0.0 release](https://github.com/OWASP/ASVS/releases/tag/v5.0.0_release)
and use its full requirements, not a moving branch or this summary.
ASVS 5.0 Authentication is **V6**, Session Management **V7**; the old V2/V3 labels
must not be used for those chapters. Examples of traceable requirements:
- V6.3.3 (L2): assess the required multi-factor/combined authentication mechanism and documented exceptions.
- V7.2.1 (L1): session verification uses a trusted backend service.
- V7.4.1 (L1): terminated sessions cannot be reused.
These examples are not the full assessment. For each applicable requirement record:
version + ID + level, control owner, scenario, evidence, pass/fail/not-applicable
with rationale. Keep unresolved requirements visible. Use the complete pinned
standard to discover omissions; no compliance claim without full applicable coverage.
## Threat model and access
- Identify assets, attacker capability, entrypoints and trust boundaries.
- Check authentication and authorization separately, including tenant/object ownership.
- Cover admin, bulk, exports, jobs, uploads, webhooks and recovery paths.
- Password hashing and lifecycle follow the security router's current policy.
- Check token lifetime, revocation, reuse detection and session termination.
- Cookie flags do not replace CSRF protection on state-changing requests.
- Step-up and MFA requirements follow the threat model and selected ASVS level.
## Input, output, secrets and data
- Parse untrusted input once at ingress; enforce domain invariants in their owner.
- Bound payload/collection sizes and validate output context.
- Use parameterized queries and scoped command/file-path handling.
- Keep secrets out of source, logs, client bundles and screenshots.
- Redact PII, restrict access, and define retention/deletion requirements.
- Apply appropriate TLS, CSP, cookie, CORS and other header policies for the real app.
## Release evidence
- Attach control-level tests, dependency/secret scans, and threat-model evidence.
- Unresolved High/Critical safety findings block under the declared security policy.
- A permitted exception needs a predeclared policy, owner, expiry, mitigation and proof;
this checklist cannot override a stricter image/artifact gate in dev-devops.
- Retain rollback/containment evidence for the actual release surface.
- Mark unavailable checks unverified, not passed. Report assessment coverage explicitly.
Implementation examples: `owasp-top10.md`; scanning recipes: `static-analysis.md`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 470k | Updated | Claude CodeCodex | Verified | Install |
| 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: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |