security

Audit plans and verify shell commands for security risks in check and exec workflows.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/huacheng/moonview --skill security-huacheng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/huacheng/moonview/tree/main/plugins/task-ai/skills/security
Command: npx skills add https://github.com/huacheng/moonview --skill security-huacheng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires core/lib.sh, and includes scripts (resource) components.

What problem does it solve?

Runtime Guardian audits plans and intercepts high-risk shell commands before execution to prevent latent attacks.

Core Features & Use Cases

  • Audits task plans for security risks prior to execution in check and exec flows.
  • Intercepts dangerous shell commands in real time and blocks unsafe actions.
  • Provides risk assessment and incident-handling guidance for unsafe plans.

Quick Start

Invoke the security audit on a notebook to verify the safety of a plan.

Frequently Asked Questions about security

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

FAQPage Schema
How do I run pre-execution security checks on shell commands in task automation?

Pre-execution security checks audit plans and verify shell commands for security risks before execution. The mechanism scans .plan.md and .target.md files, blocks dangerous commands in real time, and returns a PASS or REJECT status with a rationale.

How do I audit task plans for security risks prior to execution?

Auditing task plans for security risks involves scanning .plan.md and .target.md files for dangerous shell commands. This provides risk assessment and incident-handling guidance for unsafe plans before they are executed in check and exec workflows.

Can I use a pre-hook to block dangerous shell commands during plan development?

Yes, a pre-hook can block dangerous shell commands during plan development across notebooks. It intercepts high-risk commands in real time, preventing latent attacks by returning a REJECT status with a rationale for unsafe actions.

What do I need to set up pre-execution security checks for safe automation?

Setting up pre-execution security checks requires the core/lib.sh dependency and scripts component. This configuration enables the pre-hook to scan plan files and verify shell commands within check and exec workflows.

When should I not rely on pre-hook security checks in automation workflows?

Pre-hook security checks are limited to scanning .plan.md and .target.md files and verifying shell commands. They should not be the sole security layer for complex runtime vulnerabilities or non-shell-based execution risks outside of task automation.