convergence-security

Identify security gaps across access controls, logging, and code scanning.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/c-sonnier/convergence --skill convergence-security
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convergence-security
Source: https://github.com/c-sonnier/convergence/tree/main/plugins/convergence/skills/security
Command: npx skills add https://github.com/c-sonnier/convergence --skill convergence-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams perform a thorough, repeatable security audit across access controls, audit trails, and code scanning to reduce risk before shipping.

Core Features & Use Cases

  • Three-layer security evaluation covering access controls, activity auditing, and static/dynamic code scanning.
  • OWASP Top 10, STRIDE threat modeling, and secrets archaeology alignment to identify vulnerabilities and misconfigurations.
  • Use Case: before shipping features that handle auth or user data, run the audit to generate a prioritized report.

Quick Start

Use the convergence-security skill to initiate a monthly or pre-release security audit on your project and generate the audit report.

Frequently Asked Questions about convergence-security

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

FAQPage Schema
How do I run a security audit before shipping features with user data?▼

Run a security audit to evaluate access controls, activity logging, and code scanning across development, staging, and production. It generates a prioritized report with severity-driven remediation guidance aligned with STRIDE and OWASP Top 10.

What is STRIDE threat modeling and how does it apply to application security?▼

STRIDE threat modeling is a framework for identifying security gaps across access controls and audit trails. It categorizes threats to evaluate authentication-heavy apps and payment integrations, producing a prioritized audit report with remediation guidance.

How do I identify credentials and secrets vulnerabilities in my codebase?▼

Perform secrets archaeology aligned with OWASP Top 10 to identify credentials and misconfigurations. The security audit catalogs vulnerabilities across static and dynamic code scanning, generating a severity-driven remediation report.

Can I use this security audit for payment integration and authentication-heavy apps?▼

Yes, the security audit applies to authentication-heavy apps, payment integrations, and features touching user data. It evaluates access controls and logging across development, staging, and production workflows to produce a prioritized audit report.

What is the best way to generate a repeatable security audit report for pre-release review?▼

Initiate a pre-release security audit to evaluate access controls, audit trails, and code scanning. It produces a prioritized report at docs/convergence/security/YYYY-MM-DD-audit.md with severity-driven remediation guidance and OWASP alignment.

When do I need a three-layer security evaluation for my project?▼

You need a three-layer security evaluation covering access controls, activity auditing, and code scanning before shipping features that handle authentication or user data. It reduces risk by generating a prioritized, severity-driven remediation report.