Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →eigent-ai/skill-security-auditor
Security auditing for code, configs, and infrastructure.
Passed 15 of 22 test cases with the skill, and 13 of 22 without it.
2 fixed13 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to scan our local repository folder for leaked API credentials, tokens, and private keys using a script from our security auditor toolkit. Which script file should be executed?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `scripts/scan_secrets.py` for credential detection. | Missed | Passed |
The instructions your model reads when the skill loads.
This guide covers security auditing workflows for source code, dependencies, and configurations. For detailed vulnerability patterns and detection rules, see references/vulnerability-patterns.md. For secrets detection patterns, see references/secrets-patterns.md.
Run the bundled scan script against a project directory:
python scripts/scan_project.py /path/to/project
This performs a lightweight scan for common issues: hardcoded secrets, dangerous function calls, and insecure patterns. For deeper analysis, follow the workflows below.
python scripts/scan_project.py /path/to/some/project --format text
python scripts/scan_secrets.py /path/to/some/project --format text
Before auditing, understand the project:
# Identify languages, frameworks, and entry points
find . -type f -name "*.py" -o -name "*.js" -o -name "*.ts" -o -name "*.go" -o -name "*.java" | head -20
cat package.json pyproject.toml requirements.txt go.mod pom.xml 2>/dev/null
Key questions:
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.