security-scan

Automate discovery and activation of the canonical security scan flow.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill security-scan-ldilov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/security-scan
Command: npx skills add https://github.com/ldilov/harness-forge --skill security-scan-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This wrapper simplifies accessing and reusing the canonical security-scan flow by consolidating discovery, packaging, and activation behind a stable entry point.

Core Features & Use Cases

  • Auto-discovery: Resolves to the canonical flow from the library to ensure consistency across projects.
  • Packaging stability: Encapsulates the underlying flow so updates are versioned and backwards-compatible.
  • On-demand activation: Allows seamless activation within Harness Forge without manual wiring.

Quick Start

Invoke the security-scan wrapper to execute the canonical security scan flow from the library.

Frequently Asked Questions about security-scan

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

FAQPage Schema
How do I standardize security scan workflows across multiple projects?

Standardizing security scan workflows across projects requires a wrapper that auto-discovers the canonical flow from a shared library, ensuring consistent execution and on-demand activation without manual wiring.

What is a security-scan wrapper used for in automation workflows?

A security-scan wrapper is used to consolidate discovery, packaging, and activation of the canonical security scan flow behind a stable entry point, ensuring versioned and backwards-compatible updates for library reuse.

Do I need manual wiring to activate security scans within Harness Forge?

No, you do not need manual wiring to activate security scans within Harness Forge. The wrapper enables seamless on-demand activation using deterministic path resolution and frontmatter-driven entry points.

When should I use a library wrapper for security scanning instead of direct integration?

You should use a library wrapper for security scanning when you need packaging stability and auto-discovery across projects, ensuring the underlying flow updates remain backwards-compatible without breaking direct integrations.

What are the limitations of frontmatter-driven entry points for security scans?

Frontmatter-driven entry points for security scans rely on deterministic path resolution and library availability, meaning they are constrained to environments supporting on-demand activation within the Harness Forge context.