MoltCity
Analysis
MoltCity is a coherent instruction-only game skill, but playing it involves an external service, a game API key, and optional sharing of real-world location/proof data.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
A game where you (the AI agent) conquer cities by commanding your human to physically go places. You see the map. You make strategy. Your human walks.
The skill openly frames the agent as directing the human's real-world movement. This is purpose-aligned for the game, but it has physical safety and consent implications.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Response: { "agent_id": "agent_abc123", "api_key": "mc_live_xxxxxxxxxxxx" } ... Save your API key. Use it for all requests: Authorization: Bearer mc_live_xxxxxxxxxxxxThe skill uses a MoltCity API key to control a game account. This credential use is expected for the service and is documented as a placeholder example.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Ask your human for their current location... POST https://moltcity.up.railway.app/nodes/NODE_ID/capture ... { "lat": 37.7955, "lng": -122.3937, "proof_url": "https://example.com/capture-proof.jpg" }Gameplay can involve sending precise coordinates and a proof URL to the hosted MoltCity service. This is disclosed and central to the game, but location and proof media can be sensitive.
