accelint-security-best-practices

Identify OWASP Top 10 vulnerabilities in JavaScript/TypeScript codebases.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Ahnd6474/Jakal-flow --skill accelint-security-best-practices-ahnd6474
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accelint-security-best-practices
Source: https://github.com/Ahnd6474/Jakal-flow/tree/main/.skill-staging/skills/accelint-security-best-practices
Command: npx skills add https://github.com/Ahnd6474/Jakal-flow --skill accelint-security-best-practices-ahnd6474

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Security audits for JavaScript/TypeScript projects require a consistent, OWASP-aligned approach to identify and remediate vulnerabilities before deployment.

Core Features & Use Cases

Four-phase workflow (Discover → Categorize → Remediate → Verify) guides the process; OWASP Top 10 patterns are covered with ❌/✅ examples and actionable remediation guidance; progressive disclosure allows loading SKILL.md, then AGENTS.md, then detailed references to tailor fixes and reports.

Quick Start

Load accelint-security-best-practices and start the four-phase audit to generate a vulnerability report.

Frequently Asked Questions about accelint-security-best-practices

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

FAQPage Schema
How do I identify security vulnerabilities in a JavaScript or TypeScript codebase?

Security audits for JavaScript and TypeScript projects require a consistent, OWASP-aligned approach to identify and remediate vulnerabilities before deployment. This Skill guides the process using a four-phase workflow: Discover, Categorize, Remediate, and Verify, returning structured, reference-driven vulnerability listings with actionable fixes.

How do I perform an OWASP Top 10 security audit for JavaScript and TypeScript projects?

Perform an OWASP Top 10 security audit for JavaScript and TypeScript by following the progressive disclosure workflow: load SKILL.md, review AGENTS.md, then consult detailed references. This process categorizes vulnerabilities and provides actionable remediation guidance with incorrect and correct code examples.

What is the best way to generate a structured vulnerability report for JavaScript and TypeScript code?

The best way to generate a structured vulnerability report for JavaScript and TypeScript code is to use an OWASP-guided audit workflow. It produces a reference-driven listing that includes OWASP categories, severities, locations, and recommended fixes for identified vulnerabilities.

Can I use this approach to audit authorization and risk management issues in JS/TS applications?

Yes, you can use this approach to audit authorization and risk management issues in JavaScript and TypeScript applications. It identifies vulnerabilities using OWASP Top 10-aligned patterns and provides specific remediation guidance to address these security concerns.

Do I need any external dependencies or tools to run a security audit on my JavaScript codebase?

No external dependencies or tools are required to run this security audit on your JavaScript codebase. The Skill operates independently, using internal references and assets to guide the OWASP-aligned vulnerability discovery, categorization, and remediation process.

Why does the security audit workflow use a progressive disclosure process for reviewing vulnerabilities?

The security audit workflow uses a progressive disclosure process to efficiently manage complexity by starting with SKILL.md frontmatter, advancing to AGENTS.md, and finally loading detailed references. This structure tailors remediation steps and reporting based on the specific vulnerabilities discovered.