Multi Agent Collaboration

This package appears to implement the claimed multi-agent features, but exercise caution before installing or running it. Specific recommendations: - Do not run install.sh or npm install without inspection. Open and audit package.json, package-lock.json, and any npm lifecycle scripts (preinstall/postinstall/build) to see what external packages and scripts will run. - Review dist/index.js and the listed dist/* files for any code that makes network requests, posts data to external endpoints, or executes child processes. Pay attention to any hard-coded URLs or calls to curl/fetch/http(s). - Inspect AGENT_PROMPTS.md and other prompt files: they instruct scraping many social platforms and using tools (web_search, extract_content_from_websites). Decide if you want the agent to have network access and whether you need to provide API keys; if so, prefer supplying keys with least privilege and monitor usage. - Because the package will run npm install/build, consider installing and testing it inside an isolated environment (container, VM) and run static analysis and dependency vulnerability checks before giving it network access. - Ask the publisher for provenance: source is 'unknown' and no homepage is provided. Prefer packages with an identifiable maintainer or a public repo to review changes and history. If you want, I can: parse package.json/scripts to highlight risky lifecycle scripts, list the top dependencies, or scan the dist files for outbound network calls — tell me which file(s) to inspect first.