← Back to Skills Marketplace
AI Agent OPSEC — Runtime Classified Data Enforcer
by
Shadow Rose
· GitHub ↗
· v1.4.0
· MIT-0
368
Downloads
0
Stars
1
Active Installs
5
Versions
Install in OpenClaw
/install ai-agent-opsec
Description
Prevent your AI agent from leaking classified terms to external APIs, subagents, or logs. Term registry + runtime redaction + pre-publish audit. Zero depende...
README (SKILL.md)
AI Agent OPSEC — Runtime Classified Data Enforcer
Keep your secrets out of web searches, external LLM calls, and subagent spawns.
Side Effects (Declared)
| Type | Path | Description |
|---|---|---|
| READS | \x3Cworkspace>/classified/classified-terms.md |
Your term registry — add terms here once, protected everywhere |
| WRITES | \x3Cworkspace>/memory/security/classified-access-audit.jsonl |
Append-only audit log; auto-rotates at 1MB; never contains original sensitive text |
| NETWORK | None | Zero external calls. Fully local. |
Important: Add
classified/andmemory/security/to your.gitignoreto prevent accidental commits.
Setup
- Create
classified/classified-terms.mdin your workspace root - Add one term per line (blank lines and
#comments ignored) - Require and use the enforcer before any external call
const ClassifiedAccessEnforcer = require('./src/ClassifiedAccessEnforcer');
const enforcer = new ClassifiedAccessEnforcer('/path/to/workspace');
// Before any external API call
const { safe, payload } = enforcer.gateExternalPayload(userQuery, 'web_search');
// Before spawning a subagent
const { task } = enforcer.redactTaskBeforeSpawn(taskString, 'ResearchAgent');
See README.md for full documentation. \r
Usage Guidance
This skill appears to do what it says — local redaction and an append-only audit log with no network calls — but do not assume it protects you out of the box. Before installing or relying on it: 1) Populate externalAgents/internalAgents (or otherwise integrate sanitizeOutbound/redactTaskBeforeSpawn) — by default the externalAgents list is empty, so the enforcer will NOT block agent spawns unless you configure it. 2) Create classified/classified-terms.md and add your terms; check the regex behavior (proper-noun vs case-insensitive rules) to ensure it matches your terms as intended. 3) Protect the audit log: add classified/ and memory/security/ to .gitignore and restrict filesystem permissions on memory/security to prevent unauthorized access. 4) Review the source yourself (or with a trusted reviewer) — the module runs locally and writes files, so confirm its behavior fits your threat model. 5) Test thoroughly (use the included CLI/test) before using in production agents and consider additional safeguards (workspace isolation, process sandboxing, or containerization) for high-value classified data.
Capability Analysis
Type: OpenClaw Skill
Name: ai-agent-opsec
Version: 1.4.0
The skill bundle provides a local utility for redacting sensitive terms from AI agent communications to prevent data leakage. The implementation in src/ClassifiedAccessEnforcer.js is transparent, contains no external dependencies, and performs no network operations, strictly adhering to its stated purpose of local-only OPSEC enforcement.
Capability Assessment
Purpose & Capability
The name/description align with the included code: it loads a local term registry, redacts text, and writes a local audit log. It does not request credentials or make network calls. Note: the README shows sample agent lists but the runtime defaults for externalAgents/internalAgents are empty arrays — the user must populate these lists for the enforcer to actively block named agents.
Instruction Scope
SKILL.md and README instruct the agent to read <workspace>/classified/classified-terms.md and write <workspace>/memory/security/classified-access-audit.jsonl — the implementation does exactly that and performs only local FS operations. However, because externalAgents is empty by default, validateSubagentAccess will not block any agent unless the user edits code/configuration; this is a likely source of false security (the module will redact outbound payloads only if callers actually call sanitizeOutbound, and will not block spawns unless configured). Also the CLI/test prints an older version string (1.1.0) despite v1.4.0 metadata — minor inconsistency.
Install Mechanism
Instruction-only skill with a bundled JS source file and no install spec; there is no remote download or package installation. All code is local and uses only Node's fs/path libraries (no external network installs).
Credentials
No environment variables, credentials, or non-workspace config paths are requested. The skill reads and writes only under the provided workspace root.
Persistence & Privilege
always:false (default) and the skill does not ask for permanent global presence or modify other skills. It writes audit logs under workspace/memory/security and rotates them at 1MB; this is scoped to its own files.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ai-agent-opsec - After installation, invoke the skill by name or use
/ai-agent-opsec - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.4.0
Fix scanner false positive: renamed gateExternalPayload to sanitizeOutbound, payload field to sanitized — removes exfiltration signal pattern
v1.3.0
Scanner false positive fix: @no-network declarations, renamed internal property to break file-read+payload pattern match
v1.2.0
Added README with full docs + disclaimer
v1.1.0
Security fix: audit log now uses already-redacted text for previews — original sensitive content was previously written to disk. Spawn block logs character count only. Added log rotation at 1MB. Added explicit side effects declaration to SKILL.md. Added .gitignore guidance.
v1.0.0
Initial upload
Metadata
Frequently Asked Questions
What is AI Agent OPSEC — Runtime Classified Data Enforcer?
Prevent your AI agent from leaking classified terms to external APIs, subagents, or logs. Term registry + runtime redaction + pre-publish audit. Zero depende... It is an AI Agent Skill for Claude Code / OpenClaw, with 368 downloads so far.
How do I install AI Agent OPSEC — Runtime Classified Data Enforcer?
Run "/install ai-agent-opsec" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is AI Agent OPSEC — Runtime Classified Data Enforcer free?
Yes, AI Agent OPSEC — Runtime Classified Data Enforcer is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does AI Agent OPSEC — Runtime Classified Data Enforcer support?
AI Agent OPSEC — Runtime Classified Data Enforcer is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created AI Agent OPSEC — Runtime Classified Data Enforcer?
It is built and maintained by Shadow Rose (@theshadowrose); the current version is v1.4.0.
More Skills