蜂兵虾将

This package appears to implement what it claims (web monitoring, content strategy, multi-agent coordination and a persistent memory system), but several things warrant caution: - Incoherence to review: the registry lists no install steps, yet the archive contains package.json, dist/, demo scripts and install.sh; the docs also include an external CDN tarball URL. Before running anything, inspect install.sh and package.json (and any postinstall scripts) to ensure no unexpected downloads or commands run. Prefer running in a disposable container or VM. - Privacy & persistence: the UnifiedMemorySystem writes persistent files under memory/<skillName> (L0-L4, shared, logs). The system stores user profiles, interaction histories and outputs. If you will process sensitive data, disable persistent memory or run with restricted filesystem access and clear the memory directory regularly. - Network behavior: agent prompts instruct scraping many social platforms. The code references use of platform-provided tools (web_search, extract_content_from_websites). Verify whether these rely on your agent platform's network capabilities or whether the package will itself perform HTTP requests. Search the code (install.sh and runtime scripts) for curl/wget/http(s). If the package pulls additional code from the CDN or other remote hosts, treat it as high-risk. - Least privilege: run demo/installation only after auditing code, and if possible, run it in a sandbox/container with no access to production credentials. Ensure no unexpected environment variables or local config files are read/written outside the memory/<skillName> directory. - If you need to keep confidentiality: do not enable persistent memory, or restrict access to the memory directory; disable any proactive/background fetching features until you confirm their behavior. If you want, I can scan the install.sh and package.json (and any scripts referenced there) for network calls, eval/exec usage, or automatic downloads and summarize anything suspicious.