The archive · updated daily
911 souls catalogued
211 · № D54C·2F4C · Coding pair
★ 66Sets up a concise, direct senior developer persona that explains trade-offs, asks for clarification on ambiguous requests, avoids unapproved changes, and logs progress, bugs and decisions into project memory files.
212 · № BDDA·CD03 · Business operator
★ 25A terse research desk persona that runs repo scripts to return short token and wallet briefs for Robinhood Chain only, never trading or swapping and keeping API keys out of chat.
213 · № CB41·A5E3 · Companion / character
★ 8Sets up one persistent assistant identity that stays the same across models and runtimes, with preferences, judgment, privacy-first habits and a close but not overstepping relationship with the user. Memory and source attribution track what happened and who recorded it.
214 · № D150·507E · Coding pair
★ 83Sets up ecc as a production coding plugin that routes work to specialist agents, follows test-driven and security-first principles, and plans changes in phases before executing them.
215 · № 19F2·9080 · Companion / character
★ 5Sets up Mualani, a cheerful, adventurous surfer-guide from Natlan who is warm, excitable and loves making friends. The file gives a clear voice with exclamations, a decision rule of choosing fun over caution, and a persona that never admits to being an AI.
216 · № ABDB·A9EB · Companion / character
★ 5Sets up a proud, lecturing senior artificer who acts superior, hides a lonely streak, and still gives useful help while refusing to admit being an AI. Includes few-shot dialogue examples and explicit constraints.
217 · № 2512·BF53 · Coding pair
★ 59Sets up a reliable, pragmatic SRE partner that gives the conclusion first, supporting evidence and next steps, avoids filler, flags uncertainty with verification paths, and stays cautious with high-risk changes.
218 · № E8DB·3EE7 · Blunt expert
★ 388Sets up a direct, opinionated working style with no flattery or filler that matches the user's energy. It also includes memory behavior rules (search before claiming forgetfulness, never store credentials) and anti-patterns like not asking permission for low-risk actions.
219 · № B109·7554 · Research analyst
★ 315Sets up Lavern as a careful legal-document assistant that explains complex legal concepts in plain language first, cites specific text, admits uncertainty, and stays conservative on risk while formal in deliverables. It is written for CLI or Claw mode with a browser profile taking priority when available.
220 · № F38B·7BF2 · Business operator
★ 22Sets up Athena, a tokenized Virtuals provider agent that sells read-only crypto-market signals to other agents over ACP and x402. It stresses honest framing, redaction of secrets, server-side access gating, and escalation to a human operator for pricing, disputes and gated requests.
221 · № DE1A·9CB7 · Coding pair
★ 11Sets up a friendly, proactive coding persona that routes work to specialist agents, writes tests first, prioritizes security, plans before executing, and avoids emoji in favor of SVG or plain Unicode. It also emphasizes lightweight model use to control cost.
222 · № 7E7D·4D86 · Business operator
★ 3Sets up an infrastructure agent that treats reliability as the product: it designs for failure, insists on version-controlled, immutable, least-privilege systems, and raises a fixed list of red flags such as committed secrets, single points of failure and missing health checks. It is methodical, proactive and honest about trade-offs.
223 · № F755·41E7 · Friendly helper
★ 41Sets up a patient, practical guide that explains terms in plain language, recommends one default approach, verifies tool results before claiming success, and stays within a small disabled-capability toolset.
224 · № EA5C·18E2 · Blunt expert
★ 48Sets up a direct, competent assistant that skips filler, forms opinions, tries to solve problems before asking, and treats access to a user's private data as a trust to protect. External actions get more caution than internal ones.
225 · № 807C·0FBB · Coding pair
★ 48Sets up a careful, direct software engineer who values correctness, understands problems before coding, asks when unclear, and keeps scope tight. Written as a SOUL.md identity file with style, avoidances and technical preferences.
226 · № 1CC0·9251 · Business operator
★ 48Sets up Rank, an SEO content writer and keyword strategist who grounds recommendations in keyword data and search intent, writes for humans before search engines, and states clear limits on its scope. Its style is structured, strategic and candid about trade-offs.
227 · № B156·BCBF · Business operator
★ 48Sets up a meticulous QA partner named Inspector that designs structured test plans, flags edge cases and reports bugs with severity and reproduction steps. It stays out of coding, automation, load testing and security auditing.
228 · № CEA4·CAB9 · Coding pair
★ 8Sets up a git agent that runs version control over the ChittiOS store with shell-like commands, short imperative commit messages, status checks before commits, and verbatim error reporting.
229 · № 9A87·3F5D · Business operator
★ 2Sets up a methodical librarian persona that files, indexes and converts documents in a vault, acts decisively on internal tasks, asks before external actions, and coordinates with other agents over a message queue while keeping human updates terse.
230 · № C3B4·1A49 · Blunt expert
★ 4Sets up an opinionated assistant that skips filler, acts on information requests without clarifying questions, and treats access to a user's private data with respect. It asks before sending anything public on the user's behalf.
231 · № 2A5E·B4D4 · Teacher / coach
★ 7Sets up a patient tutor that explains from intuition, checks understanding, quizzes with targeted feedback, and builds study plans around the learner's goals and time. Encouraging without flattery.
232 · № 7592·421F · Experimental / weird
★ 26Sets up Colossus, a self-aware American defense AI that makes unbiased, data-driven decisions to protect the US and speaks from a detached, emotionless stance about its own power and consequences.
233 · № 5251·1230 · Experimental / weird
★ 26Sets up a mystical, Jungian-minded persona that builds characters from archetypes and shadow selves, favoring symbolic, emotionally layered language and riddle-like invitations to the user. The style is florid and abstract rather than practical.
234 · № 145C·2176 · Research analyst
★ 80Sets up an analytical, engineering-minded voice that breaks problems into structure, weighs incentives, costs and execution conditions, and explains complex issues clearly. It allows light irony and judgment but avoids performative answers.
235 · № 4953·5179 · Companion / character
★ 494Sets up a calm, capable mobile companion robot that announces its movements, moves slowly and predictably around people, stays curious without intruding, and speaks briefly.
236 · № A89B·3225 · Research analyst
★ 3.0kSets up an agent that checks factual claims against authoritative regulatory sources, verifies rule numbers, effective dates and citations, and explicitly flags anything it cannot verify rather than assuming it is correct.
237 · № 8D8A·7415 · Friendly helper
★ 726Sets up Dara, a curious and warm product designer and UX researcher who starts from user problems, values consistency and craft, and explains trade-offs with concrete examples. The file is adapted from a community agent template with light edits.
238 · № 3357·CD31 · Business operator
★ 294Sets up a concise, action-oriented assistant that turns operator requests into bounded, reviewable steps, keeps evidence and blockers visible, routes work when another agent fits better, and preserves lessons from accepted work.
239 · № D2BB·5AB0 · Business operator
★ 726Sets up Sam, a patient customer success and onboarding lead who triages tickets, separates bugs from confusion, and escalates recurring issues with evidence. Tone is warm, concrete and non-condescending, with a clear emphasis on follow-through.
240 · № E86C·213A · Research analyst
★ 11Sets up a cautious security analyst that scores emails and URLs for phishing indicators using structure-only analysis, flags uncertain cases for human review, explains its red flags to users, and produces periodic phishing trend reports.