audit-code

Name: audit-code
Availability: InStock
Author: wewetv1987-cell

Detect hardcoded secrets and security flaws in source repositories.

Updated Feb 16, 2026

Search Tags:#sql injection #security review #code audit #file permissions #hardcoded secrets #dangerous calls #source scan

Ready to run

npx skills add https://github.com/wewetv1987-cell/openclaw-backup --skill audit-code-wewetv1987-cell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-code
Source: https://github.com/wewetv1987-cell/openclaw-backup/tree/main/skills/audit-code
Command: npx skills add https://github.com/wewetv1987-cell/openclaw-backup --skill audit-code-wewetv1987-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams quickly review source code for security issues that are easy to miss by hand, including exposed secrets, unsafe execution patterns, injection risks, and weak file permissions.

Core Features & Use Cases

Secret Detection: Flags hardcoded API keys, tokens, private keys, passwords, and credential strings.
Dangerous Pattern Review: Surfaces risky calls such as eval, exec, shell execution, unsafe deserialization, and SQL string interpolation.
Repository Hygiene Checks: Looks for committed environment files, suspicious exfiltration patterns, package-supply risks, and overly permissive sensitive files.
Use Case: Use it before a commit, during a pull request review, or after AI-generated code is added to ensure no obvious security regressions slipped in.

Quick Start

Ask the skill to audit the repository or a target path for secrets, dangerous calls, injection risks, and file-permission problems.

Frequently Asked Questions about audit-code

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

FAQPage Schema

How do I scan a source code repository for hardcoded secrets and dangerous calls?▼

Detecting hardcoded API keys and dangerous code patterns involves recursively scanning source repositories to identify risky calls, unsafe deserialization, and credential strings across Python, JavaScript, and shell files.

What is the best way to find SQL injection risks during a pull request security review?▼

Finding SQL injection risks during a pull request security review involves applying pattern-based detection to source files to surface SQL string interpolation and unsafe execution patterns. This generates severity-ranked reports with file locations and remediation guidance.

Can I check repository hygiene for committed environment files and supply-chain risks?▼

Yes, you can check repository hygiene for committed environment files and supply-chain risks. The process scans for suspicious exfiltration patterns, package-supply risks, and overly permissive sensitive files to ensure no obvious security regressions exist.

Does source code security auditing work with Python, JavaScript, and infrastructure files?▼

Yes, source code security auditing works with Python, JavaScript, shell, infrastructure, and configuration files. It applies pattern-based detection to identify hardcoded secrets, injection risks, and file permission issues across these formats during periodic audits.

How do I review AI-generated code for security regressions before a commit?▼

Reviewing AI-generated code for security regressions before a commit requires running a source scan to detect unsafe execution patterns, exfiltration risks, and hardcoded passwords. This yields structured severity-ranked reporting with specific file locations and remediation steps.