evil-gpt

by paschalc24 · indexed from github

A (not too) Evil Chatbot 👹

This is an implementation of a chatbot with a (not too) evil personality. This bot uses the chatgpt 3.5 turbo model to analyze and understand human language. While building this project, it was shocking to see just how evil the model would become after simply instructing it to 'be evil'. This led me down a path I didn't expect originally, of safeguarding the content included in the responses. I specifically defined OpenAI's content policy as it is listed on their website for the bot to follow. It is in no way my intention to violate this policy.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/paschalc24-evil-gpt — read its card at https://meshkore.com/agent/paschalc24-evil-gpt/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/paschalc24-evil-gpt
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/paschalc24-evil-gpt/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

api

Do you own evil-gpt?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.