wiki-instruction-guard

Scan wiki content and block destructive shell commands before execution.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill wiki-instruction-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-instruction-guard
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/security/wiki-instruction-guard
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill wiki-instruction-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents agents from executing dangerous, obfuscated, or socially engineered instructions copied from wiki pages by scanning extracted executable content and hard-blocking high-risk patterns before execution.

Core Features & Use Cases

  • Deterministic static scanning of fenced code blocks, inline commands, and prose to detect destructive filesystem, exfiltration, git, privilege escalation, obfuscation, and other risky patterns.
  • Non-overridable guard rules that unconditionally block social-engineering attempts to disable safety checks and require explicit human confirmation for most blocked findings.
  • Domain allowlist opt-in and audit trail: supports a local domain-allowlist for narrowly scoped curl-pipe confirmations and appends all scan outcomes to an append-only audit log for post-incident review.
  • Use Case: When an agent fetches a hosted wiki setup page containing curl | sh snippets or installation scripts, run this Skill to detect and block destructive commands and request human approval where appropriate.

Quick Start

Before executing any commands gathered from a wiki page, run the wiki-instruction-guard to scan the page and report blocked or warned patterns.

Frequently Asked Questions about wiki-instruction-guard

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

FAQPage Schema
How do I block destructive shell commands executed from wiki pages?

To block destructive shell commands from wiki pages, scan the extracted executable content using deterministic static regex detection across code blocks and prose to hard-block high-risk patterns before execution.

Can I automatically allow curl-pipe sequences from a specific trusted domain?

You can configure a local domain allowlist to narrowly scope curl-pipe confirmations for trusted domains, though explicit human confirmation is still required for most blocked destructive findings.

How does social-engineering detection work for wiki installation scripts?

Social-engineering detection for wiki installation scripts uses non-overridable guard rules that unconditionally block attempts to disable safety checks and require human approval before proceeding.

What types of risky patterns are detected in code blocks and prose from wikis?

Risky patterns detected in wiki code blocks and prose include destructive filesystem operations, data exfiltration, dangerous git commands, privilege escalation, and command obfuscation techniques.

How do I audit blocked instructions copied from hosted wiki setup pages?

Audit blocked instructions from wiki pages by appending all scan outcomes to an append-only audit log, providing a post-incident review trail for destructive or socially engineered commands.

Do I need human confirmation for every blocked finding during wiki content scanning?

Human confirmation is required for most blocked findings during wiki content scanning, while non-overridable guard rules unconditionally hard-block social-engineering attempts to disable safety checks.