agentsclimarketplace

Security audit

Skill s-hiraoku/synapse-a2a/plugins/synapse-a2a/skills/security-audit

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.3 KB, as published. Nobody here has run it

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.

Gives 0 of the 12 instructions most audit compliance skills give

Counted across 936 of the 1,487 authors here whose files we hold, read 2026-08-06

  • group findings by severityin 44 of 936
  • Fetch latest guidelines before each reviewin 43 of 936, across 3 files
  • Check files against all fetched rulesin 42 of 936, across 2 files
  • Output findings in terse file:line formatin 41 of 936, across 3 files
  • Ask user which files to review if none specifiedin 41 of 936, across 3 files
  • Read specified files or prompt user for filesin 39 of 936, across 1 file
  • generate the audit reportin 39 of 936, across 36 files
  • assign a severity to every findingin 25 of 936
  • run automated accessibility scansin 23 of 936, across 13 files
  • map findings to WCAG criteriain 20 of 936, across 10 files
  • confirm audit scopein 19 of 936, across 9 files
  • check title tags and meta descriptions for uniquenessin 19 of 936, across 5 files

Said here and by no other author read

  • check for injection points
  • verify users cannot access unauthorized resources
  • evaluate architecture for security flaws
  • update outdated dependencies
  • check for multi-factor authentication
  • sanitize user-supplied data at trust boundaries

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.