V3 Security Overhaul

Remediates critical CVEs and implements secure-by-default patterns for Codex-flow v3.

Updated May 8, 2026
One-click install
npx skills add https://github.com/FrekiManagarm/d-chambaud --skill v3-security-overhaul-frekimanagarm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: V3 Security Overhaul
Source: https://github.com/FrekiManagarm/d-chambaud/tree/main/.agents/skills/v3-security-overhaul
Command: npx skills add https://github.com/FrekiManagarm/d-chambaud --skill v3-security-overhaul-frekimanagarm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bcrypt, zod.

What problem does it solve? Codex-flow v3 contains critical vulnerabilities including outdated dependencies, weak SHA-256 password hashing, and hardcoded credentials. This Skill orchestrates a comprehensive security overhaul to fix these CVEs and establish security-first development practices. ## Core Features & Use Cases - CVE Remediation: Fixes vulnerable dependencies (CVE-1), replaces SHA-256 with bcrypt password hashing using 12 rounds (CVE-2), and replaces hardcoded credentials with cryptographically secure random generation (CVE-3). - Secure-by-Default Patterns: Provides Zod-based input validation schemas, path traversal sanitization, and safe command execution via execFile without shell interpretation. - Parallel Agent Orchestration: Coordinates v3-security-architect, security-auditor, and test-architect agents for threat modeling, CVE fixes, and TDD security testing. - Use Case: When upgrading Codex-flow to v3, run this Skill to audit npm dependencies, migrate password hashing to bcrypt, and validate all user inputs against strict schemas before deployment. ## Quick Start Ask the AI to run the V3 security overhaul to fix the critical CVEs and apply secure input validation and password hashing patterns to the Codex-flow codebase.

Frequently Asked Questions about V3 Security Overhaul

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix weak password hashing in Node.js?▼

Replace SHA-256 hashing with bcrypt using 12 salt rounds. Import bcrypt and call bcrypt.hash(password, 12) instead of crypto.createHash, which is vulnerable to rainbow table and brute-force attacks.

How to remediate vulnerable npm dependencies?▼

Update the affected package to a patched version, such as npm update @anthropic-ai/Codex@^2.0.31, then run npm audit --audit-level high to verify no high-severity vulnerabilities remain.

How do I prevent path traversal attacks in Node.js?▼

Resolve the user-supplied path against an allowed prefix using path.resolve, then verify the result starts with the resolved allowed prefix. Throw an error if the check fails to block directory escape attempts.

Does execFile prevent command injection?▼

Yes, execFile with shell set to false passes arguments directly to the executable without shell interpretation, preventing injection through user-controlled input. Avoid exec or template-string commands with untrusted data.

What is the best way to generate secure API keys?▼

Use crypto.randomBytes(32).toString('hex') to generate a 256-bit cryptographically secure random key. Never hardcode credentials in source code, as they leak through version control and builds.