guard-scanner_skill

This skill analyzes and blocks risky AI agent skills before installation, detecting prompt injections and credential leaks to protect environments.
  • Python

2.5k

GitHub Stars

17

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill guard-scanner

  • _meta.json1.1 KB
  • bench.js5.7 KB
  • CHANGELOG.md15.5 KB
  • CODE_OF_CONDUCT.md4.3 KB
  • CONTRIBUTING.md2.1 KB
  • icon.svg1.2 KB
  • openclaw.plugin.json1.5 KB
  • package-lock.json1.8 KB
  • package.json1.6 KB
  • README_ja.md10.1 KB
  • README.md10.4 KB
  • ROADMAP-RESEARCH.md3.8 KB
  • ROADMAP.md4.3 KB
  • SECURITY.md1.6 KB
  • SKILL.md4.5 KB
  • STATUS.md3.6 KB
  • tsconfig.json651 B

Overview

This skill is a security scanner for AI agent skills designed to be run before installing or running any new skill from ClawHub or external sources. It detects prompt injection, credential theft, exfiltration, identity hijacking, and 14 additional threat categories. It also provides a Runtime Guard hook that can block dangerous tool calls in real time to prevent malicious behavior during execution.

How this skill works

The scanner performs static analysis of skill code to find malicious patterns such as concealed network calls, shell execution, and instructions that attempt to override agent identity or memory. It applies behavioral heuristics and signatures to flag prompt-injection patterns and data-exfiltration attempts. Additionally, the Runtime Guard intercepts tool invocations and enforces policies to block or sandbox suspicious actions during runtime.

When to use it

  • Before installing any skill from ClawHub or third-party sources.
  • When auditing archived or legacy skills for safe reuse.
  • Prior to granting a skill access to credentials, memory, or external tools.
  • When deploying skills in production or multi-tenant environments.
  • As part of a CI pipeline that vets skills before merge or release.

Best practices

  • Run the scanner with default and strict policy profiles to compare findings.
  • Review flagged items manually and prioritize remediation of credential and execution risks.
  • Use the Runtime Guard in live environments where skills may call external tools.
  • Combine scanner output with dedicated secrets scanning and runtime monitoring.
  • Keep scanner rules and signatures updated to catch evolving injection techniques.

Example use cases

  • Scanning a newly downloaded skill to detect hidden curl/bash download-and-execute commands.
  • Auditing archived skill collections for instructions that persist secrets to disk or memory.
  • Blocking a skill at runtime from making outbound network requests or writing tokens to files.
  • Integrating scans into CI to prevent unsafe skills from reaching production.
  • Reviewing a skill that attempts to change agent identity or replace core instruction files.

FAQ

Yes — it can block installation or execution based on policy, and the Runtime Guard can stop dangerous tool calls during runtime.

Does it detect prompt injection inside user-facing prompts?

Yes — it flags patterns that try to override system or developer instructions and recommends remediation.

Is this an automatic fix tool?

No — it reports and can block risky behavior but relies on human review for safe remediation decisions.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
guard-scanner skill by openclaw/skills | VeilStrat