Skip to content
Skills Library
Security · Review & audit

scan

/scan

Guide automated security scanning, dependency auditing, and secret detection. Use when: dependency audit, CVE scanning, secret detection, license compliance. Not for: manual threat modeling and secure design review — use /security; general code cleanliness — use /sweep. Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Guide automated security scanning, dependency auditing, and secret detection. Use when: dependency audit, CVE scanning, secret detection, license compliance. Not for: manual threat modeling and secure design review — use /security; general code cleanliness — use /sweep. Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability.

Arguments

/scan [scan type or target | 掃描類型或目標]
Original author description

Guide automated security scanning, dependency auditing, and secret detection. Use when: dependency audit, CVE scanning, secret detection, license compliance. Not for: manual threat modeling and secure design review — use /security; general code cleanliness — use /sweep. Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability.

How it works

  1. Scan Types | 掃描類型
  2. Tool Integration | 工具整合
  3. Severity Classification & SLA | 嚴重程度分類與 SLA
  4. Workflow | 工作流程
  5. Usage | 使用方式
  6. Next Steps Guidance | 下一步引導
  7. Reference | 參考
  8. Version History | 版本歷史
  9. AI Agent Behavior | AI 代理行為
  10. License | 授權
Original SKILL.md headings · 87 lines, 482 words
SKILL.md preview
---
name: scan
scope: universal
description: |
  Guide automated security scanning, dependency auditing, and secret detection.
  Use when: dependency audit, CVE scanning, secret detection, license compliance.
  Not for: manual threat modeling and secure design review — use /security; general code cleanliness — use /sweep.
  Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability.
allowed-tools: Read, Grep, Glob, Bash(npm:audit, npx:*)
argument-hint: "[scan type or target | 掃描類型或目標]"
---

# Security Scan Assistant | 安全掃描助手

Automate security scanning for dependencies, secrets, and license compliance.

自動化相依套件、機密資訊和授權合規的安全掃描。

## Scan Types | 掃描類型

| Type | Tool Examples | Purpose | 用途 |
|------|---------------|---------|------|
| **Dependency audit** | npm audit, pip-audit, Snyk | Find known CVEs in dependencies | 檢測相依套件已知 CVE |
| **Secret detection** | gitleaks, trufflehog | Find leaked credentials in code | 偵測程式碼中洩漏的憑證 |
| **License compliance** | license-checker, SPDX | Verify OSS license compatibility | 驗證開源授權相容性 |
| **SAST** | Semgrep, CodeQL | Static analysis for code patterns | 靜態分析程式碼模式 |

## Tool Integration | 工具整合

| Tool | Command | Scope | 範圍 |
|------|---------|-------|------|
| npm audit | `npm audit --json` | Node.js dependencies | Node.js 相依套件 |
| Snyk | `npx snyk test` | Multi-language deps | 多語言相依套件 |
| Trivy | `trivy fs .` | Filesystem & containers | 檔案系統與容器 |
| gitleaks | `gitleaks detect` | Git history secrets | Git 歷史機密 |
| SPDX | `npx spdx-tool` | License SBOM generation | 授權 SBOM 產出 |

## Severity Classification & SLA | 嚴重程度分類與 SLA

| Severity | SLA | Criteria | 標準 |
|----------|-----|----------|------|
| **Critical** | 24 hours | RCE, auth bypass, data exfil | 遠端執行、認證繞過、資料外洩 |
| **High** | 72 hours | Privilege escalation, SQLi | 權限提升、SQL 注入 |
| **Medium** | 2 weeks | XSS, CSRF, info disclosure | XSS、CSRF、資訊洩漏 |
| **Low** | Next sprint | Missing headers, verbose errors | 缺少 Header、冗長錯誤訊息 |

## Workflow | 工作流程

```
SCAN ──► TRIAGE ──► PRIORITIZE ──► FIX ──► VERIFY
```

1. **Scan** — Run automated scanners on codebase and dependencies
2. **Triage** — Filter false positives, confirm real vulnerabilities
3. **Prioritize** — Rank by severity and exploitability
4. **Fix** — Apply patches, update dependencies, rotate secrets
5. **Verify** — Re-scan to confirm remediation

## Usage | 使用方式

```
/scan                - Full scan (deps + secrets + license) | 完整掃描
/scan --deps         - Dependency audit only | 僅相依套件審計
/scan --secrets      - Secret detection only | 僅機密偵測
/scan --license      - License compliance check | 授權合規檢查
```

## Next Steps Guidance | 下一步引導

After `/scan` completes, the AI assistant should suggest:

> **掃描完成。建議下一步 / Scan complete. Suggested next steps:**
> - 執行 `/security` 深入安全審查 ⭐ **Recommended / 推薦** — Run deep security review
> - 執行 `/checkin` 確認修復符合提交規範 — Verify fixes meet check-in standards
> - 執行 `/commit` 提交安全修復 — Commit security fixes
> - 更新相依套件 → `npm update` 或 `pip install --upgrade` — Update dependencies

## Reference | 參考

- Core standard: [security-standards.md](../../core/security-standards.md)

## Version History | 版本歷史

| Version | Date | Changes | 變更說明 |
|---------|------|---------|----------|
| 1.0.0 | 2026-03-23 | Initial release | 初始版本 |


## AI Agent Behavior | AI 代理行為

> 完整的 AI 行為定義請參閱對應的命令文件:[`/scan`](../commands/scan.md#ai-agent-behavior--ai-代理行為)
>
> For complete AI agent behavior definition, see the corresponding command file: [`/scan`](../commands/scan.md#ai-agent-behavior--ai-代理行為)

## License | 授權

CC BY 4.0 — Documentation content

Versions

RepositoryScoreLicence
This page · AsiaOstrich/universal-dev-standards95MIT
tony/skills100MIT
zealynxsecurity/krait100MIT
koda-ai-studio/agent-bom100Apache-2.0
cwinvestments/memstack100MIT
x-cmd/x-cmd100Apache-2.0
duc01226/EasyPlatform100MIT
duc01226/EasyPlatform100MIT
wshobson/agents100MIT

Database snapshot: 13.11.2026 · package version aa8d5548747c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 84security-scan-assistant
    引导自动化安全扫描、依赖包审计与密钥检测。 Use when: 依赖包审计、CVE 扫描、密钥检测、许可证合规。 Not for: 人工的威胁建模与安全设计审查——请用 /security;一般的代码整洁度——请用 /sweep。 Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability, 扫描, 审计, 依赖包, 密钥检测.
  • 90chain-scan
    Design a dependency scanning program — CVE detection, license checks, and CI gates. Use when asked to "scan our dependencies", "set up CVE detection", or "add a dependency CI gate".
  • 100security-scan-assistant
    引導自動化安全掃描、相依套件稽核與機密偵測。 Use when: 相依套件稽核、CVE 掃描、機密偵測、授權條款合規。 Not for: 人工的威脅建模與安全設計審查——請用 /security;一般的程式碼整潔度——請用 /sweep。 Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability, 掃描, 稽核, 相依套件, 機密偵測.
  • 90security-dependency-audit
    Audits dependencies for CVEs, license risk, and transitive exposure; writes a remediation plan with ownership. Output: audit report (per package: CVE / license / fix status) plus a patch plan. Pulled by the `security` specialist. TRIGGER: "audit dependencies for CVEs in X",…
  • 100security
    This skill should be used when the user asks about "security", "vulnerability scanning", "dependency audit", "supply chain security", "license compliance", "security audit", "CVE", "OWASP", "secrets scanning", "cargo-deny", "npm audit", or needs guidance on security requirements…
  • 100vulnerability-scanning
    Automated security scanning for dependencies, code, containers with Trivy, Snyk, npm audit. Use for CI/CD security gates, pre-deployment audits, compliance requirements, or encountering CVE detection, outdated packages, license compliance, SBOM generation errors.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.