security-best-practices

Review Python, JavaScript, TypeScript, and Go code against language-specific security best practices.

1|Updated Jul 16, 2026
One-click install
npx skills add https://github.com/sota411/codex-config --skill security-best-practices-sota411
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-best-practices
Source: https://github.com/sota411/codex-config/tree/main/user-skills/security-best-practices
Command: npx skills add https://github.com/sota411/codex-config --skill security-best-practices-sota411

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing secure code and catching vulnerabilities requires deep, framework-specific knowledge that is easy to miss during everyday development. This Skill loads curated security guidance for the languages and frameworks in your project so code is written securely by default and existing issues are detected and reported. ## Core Features & Use Cases - Secure-by-default code generation: Identifies the languages and frameworks in your project (Go, Express, frontend JavaScript/TypeScript, and more) and applies matching security rules while writing new code. - Passive vulnerability detection: Flags critical issues such as SQL injection, XSS sinks, CSRF gaps, path traversal, SSRF, and weak cryptography while working in a codebase. - Prioritized security reports: On request, produces a severity-organized Markdown report with numeric finding IDs, line-number references, impact statements, and safe fix suggestions. - Use Case: Ask for a security review of an Express backend and receive a report covering session configuration, CSRF protection, CORS policy, and dependency hygiene, then have each finding fixed one at a time with regression-safe changes. ## Quick Start Ask the assistant to perform a security review of this repository and write a prioritized vulnerability report.

Frequently Asked Questions about security-best-practices

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

FAQPage Schema
How do I run a security review on my codebase?▼

Ask for a security review or audit of the project. The Skill identifies the languages and frameworks in use, loads matching reference guidance, scans for violations, and writes a severity-organized Markdown report with line-numbered findings.

What languages and frameworks does this security review cover?▼

It covers Python, JavaScript/TypeScript, and Go, with dedicated reference specs for Go backends, Express web servers, and general frontend JavaScript. If no matching reference exists, it falls back to well-known security best practices for the detected stack.

Can it fix the vulnerabilities it finds?▼

Yes. After a report is reviewed, it fixes one finding at a time with concise comments explaining the security rationale. It follows the project's existing test and commit flows to avoid regressions and avoids bundling unrelated fixes into one commit.

Does the security review work without an explicit audit request?▼

Yes, it operates passively while writing or editing code, flagging critical vulnerabilities and major deviations from security guidance as they appear. A full structured report is only produced when explicitly requested.

What are the limitations of this security guidance?▼

Guidance depends on the available reference files, so uncovered languages or frameworks rely on general best-practice knowledge. It also avoids flagging issues like missing TLS or HSTS that are typically handled by infrastructure outside the application code.