← Back to Scanner

tama-agent Security Audit Report

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

tama-agent is an AI agent skill, created by KenKaiii and published at KenKaiii/tama-agent. ClawSecure audited tama-agent across 71 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 95/100 (Safe). The finding concentrates in Permissions Manifest, including Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is tama-agent safe?

ClawSecure audited tama-agent and assigned a security score of 95/100 (Safe), identifying 1 finding across Permissions Manifest. Review the finding below before installing.

What did ClawSecure find in tama-agent?

ClawSecure identified 1 finding in tama-agent, concentrated in Permissions Manifest. The most severe is Missing config.json - agent may not be properly configured.

How was tama-agent audited?

ClawSecure ran tama-agent through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 71 files from KenKaiii/tama-agent.

What does a score of 95 mean?

ClawSecure assigned tama-agent a security score of 95/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 1 finding detected is 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 tama-agent

ClawSecure detected 1 security finding in tama-agent, spanning Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for tama-agent

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

How to Secure an MCP Server: The 2026 GuideWhat Is MCP Security? Model Context Protocol ExplainedBest AI Agent Security Tools in 2026: How to Choose

Related AI Agent Security Audits

hermes-agentScore 85/100agent-skillsScore 95/100Agent-ReachScore 85/100Self-Improving Agent (With Self-Reflection)Score 93/100wake-upScore 95/100

Scanned on May 19, 2026. tama-agent 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