Security vulnerability audit

Skill yu-iskw/coding-agent-fabric/.claude/skills/security-vulnerability-audit

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

Install

npx -y skills add yu-iskw/coding-agent-fabric --skill security-vulnerability-audit

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

One thing to look at

1 stars1 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.

SKILL.md

1.5 KB, 302 tokens by cl100k_base, as published. Nobody here has run it

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

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.
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).
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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most audit compliance skills give in 302 tokens

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

Fetch latest guidelines before each reviewin 43 of 937, across 3 files
Group findings by severityin 43 of 937
Check files against all fetched rulesin 42 of 937, across 2 files
Output findings in terse file:line formatin 41 of 937, across 3 files
Ask user which files to review if none specifiedin 41 of 937, across 3 files
Read specified files or prompt user for filesin 39 of 937, across 1 file
Generate the audit reportin 33 of 937, across 30 files
Assign a severity to every findinghere, and in 25 of 937
Run automated accessibility scansin 23 of 937, across 13 files
Output a markdown audit reportin 22 of 937
Map findings to WCAG criteriain 20 of 937, across 10 files
Confirm audit scopein 19 of 937, across 9 files

Said here and by no other author read

run the security linting script
analyze the scan output
review critical and high dependency vulnerabilities
review hard-coded secrets and configuration issues
compile a security summary report
identify the tool that found each issue

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.