← Back to Scanner

model-hierarchy Security Audit Report

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

model-hierarchy is an AI agent skill, created by zscole and published at zscole/model-hierarchy-skill. ClawSecure audited model-hierarchy across 10 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 90/100 (Safe). The 3 findings concentrate in Permissions Manifest, ReDoS and Policy Violation, including Missing config.json - agent may not be properly configured and ReDoS vulnerability: Nested quantifiers (potential…. None were rated high or critical severity.

Is model-hierarchy safe?

ClawSecure audited model-hierarchy and assigned a security score of 90/100 (Safe), identifying 3 findings across Permissions Manifest and ReDoS. Review the findings below before installing.

What did ClawSecure find in model-hierarchy?

ClawSecure identified 3 findings in model-hierarchy, concentrated in Permissions Manifest, ReDoS and Policy Violation. The most severe include Missing config.json - agent may not be properly configured and ReDoS vulnerability: Nested quantifiers (potential….

How was model-hierarchy audited?

ClawSecure ran model-hierarchy through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 10 files from zscole/model-hierarchy-skill.

What does a score of 90 mean?

ClawSecure assigned model-hierarchy a security score of 90/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 3 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 model-hierarchy

ClawSecure detected 3 security findings in model-hierarchy, spanning Permissions Manifest, ReDoS and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for model-hierarchy

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.
Fix ReDoS-prone patterns
model-hierarchy contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.
Resolve policy violations
model-hierarchy trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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

How to Secure an MCP Server: The 2026 Guide→What Is MCP Security? Model Context Protocol Explained→Why Generic Scanners Fail at AI Agent Security→

Related AI Agent Security Audits

wacliScore 95/100GitNexusScore 75/100zeroclawScore 85/100antigravity-awesome-skillsScore 75/100kicad-source-mirrorScore 95/100

Scanned on March 20, 2026. model-hierarchy 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