clawsec-perm

Scan filesystem permissions for agent identity files and session directories.

Updated Mar 9, 2026

Search Tags:#security #permissions #agent #integrity #filesystem #openclaw

Ready to run

npx skills add https://github.com/4e696b6f/clawsec-agent --skill clawsec-perm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clawsec-perm
Source: https://github.com/4e696b6f/clawsec-agent/tree/main/skills/clawsec-perm
Command: npx skills add https://github.com/4e696b6f/clawsec-agent --skill clawsec-perm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill safeguards your agent's core identity and operational integrity by rigorously checking filesystem permissions, preventing unauthorized modifications and data exposure.

Core Features & Use Cases

Identity Protection: Ensures critical files like SOUL.md and CONSTRAINTS.md are read-only to prevent hijacking.
Data Exposure Prevention: Detects and flags world-readable session logs and workspace directories.
Integrity Monitoring: Checks for unexpected recent modifications to agent identity files.
Use Case: Automatically verify that your agent's SOUL.md file has the correct read-only permissions (444) after an update, preventing potential identity override attacks.

Quick Start

Run the clawsec-perm skill to check filesystem permissions for agent identity files and workspace integrity.

Frequently Asked Questions about clawsec-perm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check filesystem permissions for agent identity files like SOUL.md?▼

You can check filesystem permissions for agent identity files like SOUL.md by scanning the workspace to validate read-only access configurations and flag world-readable session logs. This prevents unauthorized modifications and data exposure.

How do I prevent unauthorized modifications to agent workspace directories?▼

To prevent unauthorized modifications to agent workspace directories, you need to validate filesystem permissions and monitor session directories for unexpected recent changes. Scanning for correct read-only configurations stops identity hijacking.

Does filesystem permission scanning require shell access to run stat and find commands?▼

Yes, filesystem permission scanning requires shell access to execute stat and find commands. These commands perform the necessary permission and modification checks to validate agent identity files and workspace integrity.

What is the best way to secure agent identity files against data exposure?▼

The best way to secure agent identity files against data exposure is to enforce read-only permissions on critical files like SOUL.md and CONSTRAINTS.md. Validating expected security configurations detects and flags unauthorized access attempts.

Why does my agent session log show unexpected recent modifications?▼

Agent session logs show unexpected recent modifications when filesystem integrity monitoring detects changes to workspace directories. Scanning these directories against expected security configurations identifies potential unauthorized access or data exposure.

Can I use clawsec-perm to validate read-only permissions for CONSTRAINTS.md?▼

Yes, clawsec-perm validates read-only permissions for CONSTRAINTS.md by scanning the filesystem. It ensures critical agent identity files have the correct security configurations to prevent hijacking and unauthorized modifications.