Code Security Check for Openclaw

An AI-powered repository auditing tool designed to scan workspace trees for exposed credentials, tokens, and misconfigured .gitignore files prior to pushing online.

mate-matt
v1.0.1
Jun 8, 2026
0
578
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install code-security-check

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install code-security-check using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Code Security Check?

The Code Security Check skill provides developers with an intelligent, automated method to discover sensitive data leaks before code reaches public environments. Unlike conventional tools that depend on rigid regex pattern databases or brittle matching rules, this capability relies directly on large language models to interpret contextual code files. This enables it to accurately recognize novel key variations, analyze structural intent, and completely bypass regular documentation examples or false positives.

Operating natively within Openclaw Skills, this mechanism inspects active project trees for exposed API tokens, database keys, private security configurations, and unmapped tracking matrices. It evaluates remote accessibility statuses upfront to protect sensitive components without impacting workflow execution times on localized codebases.

Code Security Check Use Cases

  • Scanning active workspaces for accidentally hardcoded cloud credentials, tokens, or private encryption keys.
  • Reviewing tech-stack-specific coverage rules across localized .gitignore files before converting a codebase to open source.
  • Discovering uncommitted, high-risk metadata tracking elements lurking within active development directories.
  • Validating repository hosting configurations to guarantee that production secrets remain contained away from public git mirrors.

How Code Security Check Works

  1. Executes an exposure risk assessment gate check by auditing localized git tracking statuses, active remote linkages, and private visibility indicators.
  2. Performs technology stack discovery by scanning root environments for framework indicators like package.json, pyproject.toml, or go.mod.
  3. Conducts a structural configuration audit to verify whether essential tech-stack ignore paths are properly declared within .gitignore.
  4. Utilizes targeted glob patterns and quick content pre-filters to flag highly suspicious secret containers and private certificates.
  5. Employs deep AI context analysis on targeted files to isolate operational production credentials while redacting actual string secrets.
  6. Generates a comprehensive risk breakdown matrix summarizing tech metrics, tracking gaps, and classified severity tables.

Code Security Check Setup

Prerequisites

Ensure your agent environment has access to the local git CLI interface and GitHub CLI toolset for maximum functionality.

Usage

Trigger the automated auditing process by invoking target terms natively in conversation with the agent:

# Example conversational triggers
"check for secrets before pushing to GitHub"
"scan for API keys and check my .gitignore"

Code Security Check Data Schema & Taxonomy

The skill scans project structures and compiles operational analysis across structural parameters. Data findings are sorted dynamically through the following metadata severity schema:

Level Target Scope & Definitions
Critical Production environment API tokens, active private keys, platform permissions, and live system credentials.
High Service tokens, internal microservice configurations, and active keys identified outside ignored paths.
Medium Structural configurations missing standard security omissions, unmapped files, or credential assignments.

Structural Scanned Matrix

File structures matched during search queries include target extensions such as:

  • **/.env* configuration paths
  • **/credentials*.json metadata infrastructure files
  • **/*.pem, **/*.key, id_rsa certificates

Code Security Check Advanced Features

  • Context-aware AI structural analysis that automatically distinguishes between real secrets and placeholder documentation mock strings.
  • Dynamic gatekeeping loops that cleanly terminate background scanning executions if repositories lack public remote routes.
  • Targeted staging support which targets working trees explicitly while omitting binary archives and dependency directories.
  • Post-audit interactive remediation protocols supporting secure untracking operations using specialized cleanups like git rm --cached.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*