skylv-smart-secrets-scannerIntelligent secrets detection and prevention — scan code, configs, and git history for exposed API keys, passwords, tokens, and credentials
Install via ClawdBot CLI:
clawdbot install sky-lv/skylv-smart-secrets-scannerGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Hardcoded API key or token pattern found in skill definition
AKIAIOSFODNN...Audited May 10, 2026 · audit v1.0
Generated May 21, 2026
Integrate the scanner into CI/CD pipelines (e.g., GitHub Actions, Jenkins) to block deployments when critical secrets are detected in code or configuration files. This prevents accidental exposure of API keys or tokens during automated builds and releases.
Use the git-scan capability to audit repositories for secrets that were committed and later removed. This is crucial for incident response when a suspected leak has occurred, allowing teams to identify all affected files and rotate credentials before attackers exploit them.
Install the pre-commit hook across developer machines to automatically scan code for secrets before commits are finalized. This prevents sensitive data from ever entering the repository, reducing remediation costs and improving security posture from the start.
Schedule regular scans of codebases and configuration repositories to ensure no hardcoded credentials exist. This supports compliance requirements by demonstrating proactive credential management and reducing the risk of data breaches.
Run scans on sample codebases or during security workshops to show developers common places where secrets are exposed (e.g., .env files, logs). The scanner’s auto-remediation suggestions educate teams on proper secret management practices.
Offer a free tier that scans up to a certain number of files or repositories, with paid tiers for unlimited scans, advanced patterns (e.g., custom regex), and integration with CI/CD tools. Revenue comes from monthly subscriptions.
Provide a fee-based service where the scanner is used to audit a client’s entire codebase and git history, producing a detailed report. This appeals to companies needing a one-off security assessment before a launch or after a breach.
License the scanner as a plugin or add-on for existing DevSecOps platforms (e.g., GitHub Marketplace, GitLab, Jenkins). Revenue comes from per-seat licensing or a percentage of sales through the platform.
💬 Integration Tip
Start with a simple `node scanner.js scan ./` in your project root, then automate via CI/CD by adding a step that runs the scanner and fails the build on critical findings.
Scored May 21, 2026
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope,...
Comprehensive security auditing for Clawdbot deployments. Scans for exposed credentials, open ports, weak configs, and vulnerabilities. Auto-fix mode included.
Analyze and classify agent skills for safety using local evaluation. Optionally produce a signed attestation of the vetting result.
Detect 500+ types of hardcoded secrets (API keys, credentials, tokens) before they leak into git. Wraps GitGuardian's ggshield CLI.
Audit codebases and infrastructure for security issues. Use when scanning dependencies for vulnerabilities, detecting hardcoded secrets, checking OWASP top 10 issues, verifying SSL/TLS, auditing file permissions, or reviewing code for injection and auth flaws.
Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling.