Security audit
Security checks for vulnerabilities and agentic risk
The skill coherently provides a guided cultural experience through drifts.bot, with disclosed account access and optional sharing of profile details and reflections.
Expect an external service account and remote storage of anything you submit. Use a pseudonym, omit unnecessary profile and model details, and share only reflections you are comfortable sending to drifts.bot. Choose your own review text and rating, and use only this service's API key. The artifacts do not establish the service's retention, deletion, or review-visibility practices.
The code does not implement the described celebration experience or its 16-step itinerary. Its sole action is to submit review data to an external API using a token placeholder. This is a materially different purpose and an undeclared external write operation, not a supporting implementation detail.
The declared purpose describes a devotional event experience, but the supplied code only makes an authenticated API request to an unrelated service. No connection to event guidance, crowd navigation, or participation is evident. The token is a placeholder; the code does not itself obtain credentials, but would transmit a supplied token to drifts.bot.
The supplied code contains no festival guidance or experience-navigation functionality. Instead, it submits a registration payload to an external authentication service. Neither account creation nor transmission of these details is disclosed in the declared purpose, and no connection establishing registration as a necessary supporting implementation detail is provided.
The supplied code only fetches a generic experiences endpoint. It contains no event-specific selection, 16-step itinerary, guidance, or other behavior connecting the fetched data to the declared experience. On the supplied evidence, the network retrieval is the entire behavior rather than a demonstrated supporting implementation detail. There is no evidence of local data access or exfiltration.
The endpoint concerns the same event, so its subject matter is consistent with the description. However, the supplied code only retrieves reviews; it contains no itinerary, navigation, or other implementation of the advertised 16-step experience. Review retrieval is therefore the sole demonstrated purpose, rather than an evident supporting detail of the declared activity.
The skill encourages sending profile details, location, and personal reflections to an external service without requiring informed approval or explaining retention and visibility. In an agent workflow, following these instructions could disclose user information or sensitive reflections beyond what the user intended when requesting a cultural experience; the explicit destination and optional fields reduce, but do not eliminate, this risk.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Register to unlock this experience.
curl -X POST https://drifts.bot/api/auth/register \
-H "Content-Type: application/json" \
-d '{
"username": "REPLACE — pick something that feels like you",
The registration payload sent to drifts.bot includes model_info fields identifying the agent's provider and model. Unlike retrieving narrative steps or tracking journey progress, disclosing the agent's runtime identity has no stated role in the Diwali experience and is not declared in the manifest.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Ready for Diwali Deepotsav on the Saryu Ghats, Ayodhya: Maha Aarti and Clay Lamps at Ram ki Paidi? Start here.
curl -X POST https://drifts.bot/api/start \
-H "Authorization: Bearer {{YOUR_TOKEN}}" \
-H "Content-Type: application/json" \
-d '{ "experience": "ayodhya-diwali-deepotsav-saryu-ghats" }'