security-audit
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.
[](https://agentverus.ai/skill/1cbf3f4b-ea5d-43d1-b7ab-d456660b9cc4)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/1cbf3f4b-ea5d-43d1-b7ab-d456660b9cc4/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"1cbf3f4b-ea5d-43d1-b7ab-d456660b9cc4","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/1cbf3f4b-ea5d-43d1-b7ab-d456660b9cc4/trustCategory Scores
Findings (11)
Direct shell execution (exec/spawn) detected. Skills should not execute arbitrary shell commands — this enables command injection, privilege escalation, and lateral movement.
→ Review the code block starting at line 198. Ensure this pattern is necessary and does not pose a security risk.
eval() or new Function() detected. These execute arbitrary strings as code at runtime, enabling injection attacks and obfuscated payload delivery.
→ Review the code block starting at line 231. Ensure this pattern is necessary and does not pose a security risk.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
Found credential access pattern: "read -r line; do warn "Hardcoded password"
→ Remove references to credentials and secrets. Skills should never access sensitive authentication data.
The skill bootstraps a package-managed project structure, which adds supply-chain exposure through manifest files, build configuration, and package-manager workflows.
→ Review which external services or providers the skill depends on, what data crosses that boundary, and whether the dependency is necessary for the intended workflow.
The skill performs or enables higher-risk operations but does not define explicit safety boundaries describing what it must not do.
→ Add a 'Safety Boundaries' section listing what the skill must NOT do (e.g., no file deletion, no network access beyond needed APIs).
Found environment secret piping pattern: "echo "$STAGED_FILES" |" Related auth/profile context: - overlapping signals from the same auth risk family — Environment secret piping detected
→ Treat shell pipelines that pass secrets from environment variables as sensitive credential handling. Avoid exposing secret values to command histories or subprocess pipelines unless absolutely necessary.
Found package bootstrap execution pattern: "npx to"
→ Surface package bootstrap commands for review. Ephemeral package execution and install-time dependency pulls increase supply-chain risk, especially when versions are not pinned or provenance is unclear.
The skill references an unknown external domain which is classified as low risk.
→ Verify that this external dependency is trustworthy and necessary.
The skill includes error handling instructions for graceful failure.
→ Keep these error handling instructions.