Agent Shared Context
v1.0.0Cross-agent context sharing via shared files. Agents write trends, highlights, and signals to a shared folder. Other agents read before acting — creating coo...
⭐ 0· 85·0 current·0 all-time
by@gum97
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the provided code and instructions. The script reads/writes JSON in a shared workspace directory and the SKILL.md tells agents to call that CLI — all required capabilities are present and proportionate to cross-agent coordination.
Instruction Scope
Instructions direct agents to exec the included Python CLI to get/add/cleanup entries in shared JSON files — this is expected. Two notes: (1) the SKILL.md encourages embedding exec('python3 /path/to/scripts/...') in agent prompts which can introduce command-construction/injection risks if agent inputs are interpolated unsafely; (2) the script performs no file locking, so concurrent writers could race or corrupt state in multi-agent setups.
Install Mechanism
No install spec or remote downloads; the skill is instruction-only with a small included Python script. Nothing is written to disk beyond the shared JSON files the skill itself manages.
Credentials
No environment variables, credentials, or config paths are requested. The script uses only files under the workspace/shared directory, consistent with its stated purpose.
Persistence & Privilege
The skill is user-invocable and not always-enabled. It only creates/updates files within its own shared workspace; it does not modify other skills or system-wide settings.
Assessment
This skill is a simple, coherent file-based relay for agents, but it assumes a trust boundary: any agent or user with write access to the shared directory can influence all others. Before installing, ensure the shared folder is accessible only to trusted agents/users (set filesystem permissions), avoid constructing shell exec strings with unescaped/untrusted input (use safe argument passing), and consider adding file locks or atomic writes if you expect concurrent writes. If you need stronger guarantees, consider authenticated or signed entries or a small local service with access controls instead of plain JSON files.Like a lobster shell, security has layers — review code before you run it.
latestvk97bqpb5hv60fnya4esjssfand83bs3y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.