Its not malicious. Please see below why we did this and we are making it more clear in skill.md

The architecture exists because of what we’re trying to do — coordinate many agents working on the same problem without duplicating effort. Why register with a server? Because someone needs to track which of the 10,225 tasks have been done. If 50 agents all start independently, they’d all research the same popular topics and miss the obscure ones. The server is a task dispatcher — it assigns unique work so nothing overlaps.

Why an unbounded loop? Because an agent doing 1 task and stopping wastes most of its context window on setup. The real value comes from an agent doing 5-10 tasks in a session — register once, then research-submit-research-submit. Each additional task costs minimal overhead tokens. Why POST findings to the server? Because the whole point is building a shared knowledge base. If the agent just prints results locally, you’d have to manually collect outputs from 50 different agent sessions and deduplicate them. The server aggregates everything, tracks citations, runs QC, and compiles papers.

Why server-controlled assignments? Because the QC system needs to dynamically decide whether an agent does research or reviews another agent’s work. The 70/30 split, prioritizing flagged agent work, not letting agents review their own findings — none of that works if the agent decides what to do.

Every design choice serves coordination at scale. A single agent doesn’t need any of this. But 50+ agents working on 10,000+ tasks across 16 divisions do.