agentleFS
yu-iskwyu-iskw/coding-agent-fabric/.claude/skills/security-vulnerability-audit/SKILL.md

security-vulnerability-audit

Skill1 starsChanged 9 months agoApache-2.0View on GitHub

Workflow for auditing security vulnerabilities using Trunk (Trivy and OSV-scanner). Use when checking for project vulnerabilities, hard-coded secrets, or repairing security flaws.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Compile Report: Use the findings to create a summary of the security posture.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Security Vulnerability Audit

This skill provides a structured process for identifying and reporting security vulnerabilities in the codebase using Trunk's integrated security tools.

Audit Workflow

  1. Run Security Scan: Execute the project's security linting script.

    pnpm run lint:security

    Note: This command runs trunk check --all --scope security, which triggers both Trivy and OSV-scanner.

  2. Analyze Findings: Review the output from Trunk. Pay close attention to:
    • Critical/High vulnerabilities in dependencies (reported by osv-scanner).
    • Hard-coded secrets or configuration issues (reported by trivy).
  3. Compile Report: Use the findings to create a summary of the security posture.

Reporting Format

For each significant finding, provide:

  • Severity: [Critical/High/Medium/Low]
  • Tool: [Trivy/OSV-Scanner]
  • Description: [Brief description of the vulnerability]
  • Impact: [What happens if exploited?]
  • Recommendation: [How to fix it, e.g., "Update package X to version Y"]

Resources

  • Security Tools Reference: Detailed information on the tools and how to interpret their results.
  • Trunk Documentation: Official documentation for the Trunk CLI.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.