s-hiraoku/synapse-a2a

security-audit

>- General-purpose security auditing guide. Covers OWASP Top 10, dependency vulnerabilities, authentication, authorization, input validation, and secret management. Use this when performing a security review or audit.

First seen Feb 11, 2026

Installation

$ npx skills add s-hiraoku/synapse-a2a --skill security-audit

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from s-hiraoku/synapse-a2a · top by installs.

npx skills add s-hiraoku/synapse-a2a

Browse all from s-hiraoku/synapse-a2a

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 13
License MIT
Default branch main
Open issues 22
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,319 B
  • docs SUMMARY.md 236 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 161 installs

SKILL.md

Security Audit Skill

This skill provides a comprehensive framework for security auditing, ensuring that common vulnerabilities are identified and addressed during development and review.

Audit Checklist

1. OWASP Top 10 & Common Vulnerabilities

  • Injection: Check for SQL, Command, or NoSQL injection points. Ensure parameterized queries or proper escaping is used.
  • Broken Access Control: Verify that users cannot access resources outside of their intended permissions.
  • Insecure Design: Evaluate the overall architecture for security flaws.
  • Cryptographic Failures: Ensure sensitive data (passwords, PII) is encrypted at rest and in transit using modern algorithms (e.g., AES-256, TLS 1.3).

2. Dependency Management

  • Vulnerability Scanning: Check for known vulnerabilities in third-party libraries (e.g., using npm audit, pip-audit, or snyk).
  • Outdated Packages: Identify and update significantly outdated dependencies.

3. Authentication & Authorization

  • Credential Management: Ensure passwords are never stored in plain text (use Argon2, bcrypt, or scrypt).
  • Session Management: Verify secure session handling (HttpOnly, Secure, SameSite flags for cookies).
  • MFA/2FA: Check for the implementation or requirement of multi-factor authentication where appropriate.

4. Input Validation & Data Handling

  • Sanitization: Validate and sanitize all user-supplied data at the trust boundary.
  • Encoding: Ensure output encoding is used to prevent Cross-Site Scripting (XSS).
  • Secret Management: Confirm that API keys, secrets, and credentials are NOT committed to the repository (use environment variables or secret managers).

Usage Guidelines

When asked to "audit" or "perform a security review":

  1. Systematically go through each category above.
  2. For each finding, categorize it by severity (Critical, High, Medium, Low).
  3. Provide clear remediation steps for every identified issue.
  4. Document any positive security practices already in place.