What problem does it solve?
NanoClaw agent runtimes currently lack a defined, container-safe way to monitor host-managed traffic for outbound secret exfiltration and inbound command injection. This Skill provides the specification baseline, safety contract, and signed release verification procedure that builders follow to implement that monitoring without breaking container isolation.
Core Features & Use Cases
- Specification Baseline: Ships a full SPEC.md defining the detector core, host service, MCP tool surface (clawsec_traffic_status, clawsec_traffic_findings, clawsec_traffic_check_config), and operator interface for runtime traffic monitoring.
- Safety Contract: Enforces opt-in, detect-and-log defaults, host-held CA private keys, redacted snippets, and no blocking or automatic trust-store changes in the first implementation.
- Signed Release Verification: Provides a complete shell procedure to verify checksums.json, checksums.sig, signing-public.pem, the archive hash, and SKILL.md/skill.json checksums before standalone installation.
- Use Case: A builder extending NanoClaw uses this scaffold to implement HTTP proxy inspection that detects AI API keys and AWS credentials leaving the runtime, while exposing only redacted findings to the container via MCP tools.
Quick Start
Ask your agent to install the nanoclaw-traffic-guardian skill from prompt-security/clawsec and then read SPEC.md to plan the host-side proxy implementation.