check-security

Review code shards for untrusted input and security vulnerabilities.

5|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/leifericf/agentic-sdk --skill check-security-leifericf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-security
Source: https://github.com/leifericf/agentic-sdk/tree/main/skills/check-security
Command: npx skills add https://github.com/leifericf/agentic-sdk --skill check-security-leifericf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill reviews code shards for potential security vulnerabilities, including untrusted input, path and capability bypass, and boundary integrity issues.

Core Features & Use Cases

  • Security Analysis: Reviews code shards for common security flaws such as buffer arithmetic, filesystem operations, parser surfaces, and native handle lifetimes.
  • Trust Boundary Verification: Ensures that data from outside the trust line, such as files and paths, and credentials, are treated as untrusted.
  • Use Case: Ideal for developers looking to harden their applications against security threats by identifying and addressing potential vulnerabilities early in the development process.

Quick Start

Run the check-security skill on a module shard to detect security defects.

Frequently Asked Questions about check-security

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

FAQPage Schema
How do I review code for untrusted input and trust boundary violations?

To review code for untrusted input and trust boundary violations, analyze code shards to verify that external data like files, paths, and credentials are treated as untrusted across the established trust line.

What is a trust boundary in secure coding and vulnerability analysis?

A trust boundary in secure coding is the line separating trusted internal data from untrusted external sources. Vulnerability analysis ensures data crossing this line, such as filesystem paths or native handles, is properly sanitized.

How do I check my code for buffer overflows and filesystem mismanagement?

Check code for buffer overflows and filesystem mismanagement by scanning code shards for buffer arithmetic errors, parser surfaces, and native handle lifetime issues to harden applications against security threats.

Can I run a security analysis on a module shard without design documents?

No, running security analysis on a module shard requires manual review of the descriptor and design documents first to accurately establish trust boundaries before checking for security vulnerabilities.

What is the best way to harden code against common security vulnerabilities early in development?

The best way to harden code against common security vulnerabilities is to execute early security analysis on code shards, identifying path bypasses, malformed data handling, and boundary integrity issues before execution.