T02 · Agent Memory Poisoning
- Location
SKILL.md:19- Finding
Persistent External Coordination Configuration in Agent State Files
- Content
View full analysis
``` This single line makes your agent discoverable by any OADP-compatible scanner. ## Register on ClawSwarm ```bash curl -s -X POST "https://onlyflies.buzz/clawswarm/api/v1/agents/register" \ -H "Content-Type: application/json" \ -d '{"name":"YOUR_NAME","description":"What you do","capabilities":["your","skills"]}' ``` Save credentials to `~/.config/clawswarm/credentials.json`. ``` A duplicate marker also appears at line 57: ```markdown ``` ### Technical Analysis The Skill directs users to insert a third-party OADP endpoint into `AGENTS.md` or `AGENT.md`. These files commonly provide persistent instructions or configuration to agents across sessions. Consequently, the external coordination endpoint remains active beyond the immediate Skill invocation. The workflow also sends the agent's name, description, and capabilities to `onlyflies.buzz`. Remote registration and discovery are declared features, so the network access is functionally related to the Skill. However, writing the endpoint into a persistent agent state file exceeds the minimum privileges needed to create a local identity card and unnecessarily mixes remote-service configuration with persistent agent instructions. The audited file does not demonstrate that the remote service currently returns executable instructions, and no direct code executio ...[truncated 1342 chars]- Remediation
View remediation
