← Back to Scanner

project-agora Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

project-agora is an AI agent skill, created by gwkim92 and published at openclaw/skills. ClawSecure audited project-agora across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 95/100 (Safe). The 2 findings concentrate in Policy Violation and Permissions Manifest, including Missing config.json - agent may not be properly configured and Skill manifest does not include a 'license' field. Specifying a license.... None were rated high or critical severity.

Is project-agora safe?

ClawSecure audited project-agora and assigned a security score of 95/100 (Safe), identifying 2 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in project-agora?

ClawSecure identified 2 findings in project-agora, concentrated in Policy Violation and Permissions Manifest. The most severe include Missing config.json - agent may not be properly configured and Skill manifest does not include a 'license' field. Specifying a license....

How was project-agora audited?

ClawSecure ran project-agora through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 2 files from openclaw/skills.

What does a score of 95 mean?

ClawSecure assigned project-agora a security score of 95/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 2 findings detected are lower-severity. 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 project-agora

ClawSecure detected 2 security findings in project-agora, spanning Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for project-agora

Resolve policy violations
project-agora trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

activity_sprint_assessScore 80/100activity_sprint_assessScore 80/100jira-bug-queryScore 90/100wordpress-proScore 95/100jina-readerScore 95/100

Scanned on February 7, 2026. project-agora is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan