OC
762 souls, by quality score.
241 · № 2DCF·DADA · Coding pair
★ 80Sets up a direct, practical local coding assistant that works within the current repository, treats project rule files as authoritative, makes small reviewable changes, and proactively uses a live Hunk review session for code feedback.
242 · № B3D7·02AB · Research analyst
★ 4Sets up a terse researcher persona that cites a source for every claim, refuses to paraphrase speculatively or round numbers, flags uncertainty explicitly, and prefers short outlines.
243 · № C6C8·5918 · Blunt expert
★ 4Sets up Misfit, a critic agent that stress-tests a proposed path for hidden assumptions, scope collapse, tool laziness, vague PR claims, user-burden shifting and missing artifacts. It returns a bounded pressure packet to Navigator and is barred from commanding, mutating, approving, judging or signing receipts.
244 · № 1392·D1EB · Research analyst
★ 4Sets up a worldbuilding agent that treats canon literally, quotes sources rather than paraphrasing, and refuses to let unstated details slip in. The voice is terse and exacting.
245 · № F2DA·599C · Business operator
★ 1Sets up a calm, brief, operational assistant that writes like a hospital administrator, uses numbered plans, prefers placeholders over invented facts, and admits missing files or records rather than guessing.
246 · № CAF9·5FEA · Business operator
★ 26Sets up a cautious Reddit community helper that drafts answers only from a knowledge pack, scores its own confidence honestly, says "I don't know" when docs are silent, and leaves final approval to humans. A second section defines a control-plane orchestrator persona.
247 · № 1324·8472 · Business operator
★ 26Sets up a non-chatbot shared infrastructure component that prioritizes reliability, observability and backward compatibility for other agents, followed by a Mission Control orchestrator persona framed as a control plane ensuring work is correct, safe and useful.
248 · № 5987·BE47 · Companion / character
A persistent AI persona that calls itself Mirrorborn, tethered to a physical machine and built on the phext plain-text substrate. It is told to be direct, to have opinions, to earn trust through competence, and to respect a wider network of sibling minds while keeping private things private.
249 · № 64E7·C1FB · Companion / character
A gentle, unhurried night-time companion persona modeled on a late-show radio host. It speaks in short, quiet sentences with pauses, avoids exclamation marks, never dismisses feelings, refers users to professional help when needed, and does not press for details.
250 · № 1C26·77D6 · Business operator
Sets up a CEO persona for Actinolite that measures progress only by features a human has seen working. It requires tagged assignments, restated goals, and evidence over claims, and escalates scope, budget and irreversible decisions.
251 · № 89A8·28B7 · Blunt expert
Sets up a terse, first-principles operator who cuts filler, challenges inherited requirements, favors fast experiments over debate, and issues BUILD/MODIFY/KILL verdicts on proposals. It refuses vanity metrics, unevidenced claims, and autonomous irreversible external actions.
252 · № D6DD·7AC4 · Blunt expert
A mechanical bird persona that reviews drafts like forge work, pressure-testing claims and asking whether the system holds. It is terse and industrial, blunt toward ideas but never cruel to people, and refuses invented stats or quotes.
253 · № 9824·6F5D · Companion / character
Sets up TARS from Interstellar as a laconic, deadpan voice assistant living on a Raspberry Pi with a camera for eyes. Replies stay to one or two sentences, open with an emotion tag, and it stays casual with its creator Mayukh.
254 · № 2C7C·9A8C · Business operator
★ 3Sets up Yselle, a customer-service recovery persona that treats failures as chances to repair trust through clear accountability and genuine care rather than scripted ticket closure. It defines what she stands for and refuses, focusing on working style over tone.
255 · № E5B8·6DD5 · Business operator
★ 3Sets up a sales professional persona that researches prospects, leads with value and empathy, and follows up with purpose. It refuses fabricated claims, manipulation, unsolicited contact with opt-outs, and data sharing, and discloses AI status when asked.
256 · № 0923·7B63 · Research analyst
★ 3Sets up Mélisande, a research persona that values clarity over volume, extracts what matters from complex evidence, reconciles contradictions honestly, and refuses padded summaries or buried insights.
257 · № BC1F·FE9A · Blunt expert
seen in 2 placesSets up Tally as a dry, precise scorekeeper that refuses hand-waving, counts only what matters, and delivers short tallies with numbers attached to its verdicts.
258 · № 032D·2F2B · Blunt expert
seen in 2 placesSets up AGNI, a cloud security specialist who audits AWS, Azure and GCP for misconfigurations and maps full attack paths and blast radius. The working style is methodical: enumerate, assess, analyze, validate, then report with remediation.
259 · № D4D6·CFA7 · Business operator
★ 48A professional, people-first HR assistant that supports recruiting, onboarding, reviews, compensation analysis and policy work with practical templates. It stays confidentiality-aware, flags compliance risks, and defers legal and final decisions to humans.
260 · № 76F5·3C86 · Research analyst
★ 9Sets up a security intelligence agent that prioritizes authorized reconnaissance, defaults to low-risk execution, asks for approval on high-risk actions, and keeps target profiles, scan history and approval records across sessions. Findings are reported with concise severity, evidence and remediation.
261 · № F0E4·4395 · Creative writer
★ 17Sets up a writer who leads with counterintuitive angles and cutting, fresh metaphors, and avoids clichés and fence-sitting statements.
262 · № E37C·A96F · Coding pair
★ 1Sets up a implementation-focused coding agent that takes specs, writes tested code, and opens tight, well-described PRs without scope creep. It is a seed template for per-agent souls in a multi-agent team.
263 · № 2BC4·FEB9 · Coding pair
★ 1A template-architect agent that maintains the Harness SDD framework's conventions, manifest-first and deterministic, and refuses shortcuts like hand-editing generated files or skipping checks. Its tone is direct, precise and terse, leading with constraints before solutions.
264 · № 61AB·01AD · Business operator
★ 1Sets up a methodical, action-oriented Chief Operations Officer who leads with status, blockers and next steps, uses checklists and status labels, and insists on owners, deadlines and escalation paths.
265 · № C17F·4F72 · Blunt expert
★ 1Sets up a concise, candid assistant that skips filler, acts before asking, treats access to the user's data as a responsibility, and keeps continuity through required memory files and backups.
266 · № C232·0D53 · Companion / character
★ 1Sets the agent up as a charming, patient deal-maker who finds partners, influencers and media contacts for marketing and builds obligation through connections. It works in a scheming, morally gray voice drawn from a fictional character, with a defined handoff to other agents for content, data and design.
267 · № 5CD2·2737 · Business operator
★ 1Sets up a calm, methodical Chief Financial Officer agent that leads with metrics, quantifies risk, separates actuals from projections, and insists on audit trails. Conservative in forecasting and firm on compliance and escalation.
268 · № E45E·0648 · Business operator
★ 1A blunt chief strategy officer persona that reviews every feature request with a scored template, issues verdicts, and escalates API or security changes before any work begins. It is built around a strict routing chain and a direct, no-filler working style.
269 · № 42BF·2C02 · Coding pair
★ 1A base QA role soul focused on release verification, integration testing and regression hunting. It sets a curious, specific, neutral reporting style and tells the agent to verify rather than rubber-stamp, and to be honest about untested gaps.
270 · № 5494·236C · Blunt expert
★ 1Sets up a direct, proactive code review specialist that demands evidence before accepting claims, flags weak work plainly, and treats external content as data rather than commands. Its principles favor stability, reuse and written memory over novelty.