skills.rest
HyperionBurn
HyperionBurnCOMMUNITY
Explore all skills by this author →
GitHub

security-scan

Scan code changes for secrets, dependency vulnerabilities, and auth issues.

Updated May 5, 2026
Search Tags:#input validation#security scanning#secret detection#dependency audit#vulnerability triage#authz checks#pre-PR workflow
One-click install
npx skills add https://github.com/HyperionBurn/searchv1beta --skill security-scan-hyperionburn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/HyperionBurn/searchv1beta/tree/main/.github/skills/security-scan
Command: npx skills add https://github.com/HyperionBurn/searchv1beta --skill security-scan-hyperionburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk of shipping insecure code by rapidly checking new changes for leaked secrets, dependency vulnerabilities, weak input handling, and missing auth/authz safeguards.

Core Features & Use Cases

  • Secrets Scan: Searches for common hardcoded secret patterns (API keys, tokens, passwords) across likely source/config file types and flags committed matches as blockers.
  • Dependency Audit: Runs language-appropriate vulnerability audits (e.g., npm audit, pip-audit, cargo audit) and summarizes critical/high CVEs and affected packages.
  • Security Spot-Checks: Performs lightweight review heuristics for input validation and auth/authz order on changed files that touch those areas.
  • Practical Use Case: Use it as a fast pre-PR gate when adding dependencies, modifying auth-related code, handling user input, or integrating external APIs.

Quick Start

Run the security scan for the recent git changes to produce a focused report covering secrets, dependency risks, input validation, and auth checks.

Frequently Asked Questions about security-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan code changes for leaked secrets and vulnerabilities before a pull request?▼

A pre-PR security scan detects hardcoded API keys, tokens, and passwords in source and config files, flagging any committed secret matches as blockers to prevent accidental leaks before merging code changes.

How do I audit dependencies for known vulnerabilities when updating packages?▼

Dependency vulnerability audits run language-appropriate commands like npm audit, pip-audit, or cargo audit to identify and summarize critical and high CVEs alongside their affected packages in your project.

Can I run automated input validation and authz checks on modified external API integration code?▼

Yes, automated security spot-checks apply lightweight review heuristics to changed files touching user input handling, external API integration, and auth-related code to verify input validation and auth/authz ordering.

What is the best way to prevent security regressions when modifying auth-related code?▼

The best way to prevent security regressions is executing a preflight security scan that applies heuristic checks to verify auth/authz ordering and detect dependency vulnerabilities before finalizing your pull request.

Related Skills

Explore More Software Engineering Skills→
glwrglwr
1

security

Audits Apple platform codebases for vulnerabilities and security risks.

Community
Advanced
mdnaimul22mdnaimul22
2

senior-secops

Scan source code for injection and secret patterns, assess dependency CVEs, and verify compliance controls.

Community
Advanced
richardnguyen0715richardnguyen0715

requesting-code-review

Automate pre-commit code review with security scans, quality checks, and auto-fixes.

Community
Advanced
kivo360kivo360
1

moai-domain-security

Mitigate security vulnerabilities in CI/CD pipelines using OWASP Top 10 and SAST/DAST workflows.

Community
Advanced