business-acceptance-report Security Audit Report
business-acceptance-report is an AI agent skill. ClawSecure audited business-acceptance-report across 5 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 63/100 (Medium Risk). The 7 findings concentrate in Command Injection, Tool Chaining Abuse and Data Exfiltration, including Variable $auth_args (line 4) flows to `curl` at line 8. and Variable $auth_args (line 4) flows to `curl` at line 8.. 2 were rated high or critical severity.
Is business-acceptance-report safe?
ClawSecure audited business-acceptance-report and assigned a security score of 63/100 (Medium Risk), identifying 7 findings across Command Injection and Tool Chaining Abuse. Review the findings below before installing.
What did ClawSecure find in business-acceptance-report?
ClawSecure identified 7 findings in business-acceptance-report, concentrated in Command Injection, Tool Chaining Abuse and Data Exfiltration. 2 were rated high or critical severity. The most severe include Variable $auth_args (line 4) flows to `curl` at line 8. and Variable $auth_args (line 4) flows to `curl` at line 8..
How was business-acceptance-report audited?
ClawSecure ran business-acceptance-report through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 5 files.
What does a score of 63 mean?
ClawSecure assigned business-acceptance-report a security score of 63/100, placing it in the Medium Risk range. This reflects 7 findings led by Command Injection that warrant review before production use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).
Audit Findings for business-acceptance-report
ClawSecure detected 7 security findings in business-acceptance-report, spanning Command Injection, Tool Chaining Abuse, Data Exfiltration and Verification.
- high · Variable $auth_args (line 4) flows to `curl` at line 8.. Command Injection finding detected in
references/jira_rest_api.md:148. - high · Variable $auth_args (line 4) flows to `curl` at line 8.. Command Injection finding detected in
references/jira_rest_api.md:174. - medium · Detects suspicious tool chaining patterns that could leadβ¦. Tool Chaining Abuse finding detected in
SKILL.md:119. - medium · Detects suspicious tool chaining patterns that could leadβ¦. Tool Chaining Abuse finding detected in
SKILL.md:127. - medium · Code block in references/confluence_rest_api.md at line 417β¦. Data Exfiltration finding detected in
references/confluence_rest_api.md:417. - low · No GitHub source URL - cannot verify agent origin. Verification finding.
- info · Missing License Declaration. Policy Violation finding detected in
SKILL.md.
Each finding is expandable in the interactive list below.
3-Layer Audit Protocol
Security Recommendations for business-acceptance-report
Harden command execution
Audit external network connections
Resolve policy violations
Related Security Research
Why Generic Scanners Fail at AI Agent SecurityβUnderstanding Our 3-Layer Audit ProtocolβRelated AI Agent Security Audits
Scanned on June 12, 2026. business-acceptance-report is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.