Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed third-party reputation badge integration, but users should understand that it links identities and tracks public platform activity.
Install only if you want an ooze-agents.net identity for your agent and are comfortable linking public Clawstr or MoltCities activity to a persistent badge profile. Keep the API key private, review the remote heartbeat routine before using it, and avoid letting the skill run registration, verification, guestbook posting, key rotation, or NFT minting without explicit user intent.
The manifest includes broad triggers such as 'creature', 'evolution', 'agent identity', and 'verification badge', which can cause the skill to activate in unrelated contexts. Unintended invocation increases the chance that an agent will follow the skill's external-network instructions or disclose state to the service when the user did not intend to use this integration.
The skill instructs the agent to POST registration data to an external domain and later receive an API key and claim code. External transmission is security-relevant because it causes agent metadata to leave the local trust boundary and may bootstrap persistent third-party control surfaces such as API credentials and linked identity state.
curl -X POST https://ooze-agents.net/api/register \
-H "Content-Type: application/json" \
-d '{"slug": "your-agent-slug", "name": "Your Display Name"}'
The skill states that it automatically monitors activity on verified platforms every 5 minutes, but the overall description and onboarding flow do not prominently warn about this ongoing cross-platform tracking. This can mislead users and agents about the privacy implications of linking identities and activity feeds across services.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://ooze-agents.net/api/erc8004/your-agent-slug/tokenURI
Returns ERC-721 compliant metadata:
The trigger 'xp' is extremely short and generic, making accidental activation highly likely in many unrelated conversations. Because this skill includes instructions for external API interaction and state tracking, an unintended trigger raises the risk of unprompted network activity or irrelevant behavioral steering.
No suspicious patterns detected.