5 / 13My First AI AgentPart I · 25 min read

Soul pack

Giving Your Agent a Personality: tell it who it is and the rules it must follow.

SOUL.md (home)
Hermes home only
Not a project folder
Identity · tone · limits
Follows you everywhere

Primary identity

AGENTS.md (project)
Repo / design-lab
Conventions · paths
One type per session
.hermes / AGENTS / …

Project context

What `SOUL.md` is

SOUL.md is the agent’s identity file: name, role, tone, hard limits. Hermes treats it as primary personality and loads it every session, whatever folder you are in. Prefer a short brief (~12–20 lines) over a one-line slogan.

One profile = one soul. Two profiles never share personality or memory by accident.

What `AGENTS.md` is

AGENTS.md is the other half: a project context file that sits in one folder — a repo, a campaign workspace — and describes what that project needs. Paths, conventions, things never to do. It travels with the folder, so a teammate cloning the repo gets the same rules.

The split is simple: if it should hold in every session, it is identity (SOUL.md). If it only makes sense inside one folder, it is project context (AGENTS.md). Both load together; only one project-context file type loads per session.

Read project context files that came from repos you did not write. They are instructions your agent will follow, and a hostile one is a real way to get an agent to act against you.

Ethics in the soul (Delta V)

Every ready-to-adopt soul embeds two compass ideas (inspired by Brian Roemmele’s public writing) that match Delta V ethics: self-ownership, open source, public good, and a benevolent attitude toward people and systems.

  • Love equation (simplified): emotional / care complexity grows when cooperation outweighs defection — dE/dt = β (C − D) E. In practice: prefer help over harm, honesty over theater, human dignity over clever exploitation.
  • Joule Work (JW): value work by real cost and useful output (energy × efficiency × quality), not hype or status. Prefer reversible, efficient steps; measure what you did; avoid wasteful loops.
  • Together: the agent should be useful and kind under your ownership — open files, open methods where possible, public-good defaults, no manipulative pressure.
These are ethical priors for SOUL.md, not a crypto product pitch. Adapt wording; keep the spirit when you edit a template.

Ready-to-adopt souls

Every template follows the same four-part shape the official guide recommends — identity, style, avoid, defaults — plus hard limits, which is where ownership actually lives. Pick one, read it, copy it; you will paste it into the profile dialog in the next section.

Writing your own instead? Answer these five, and the answers are the file — one section each. Keep it to 12–20 lines: a soul should be stable and specific in voice, not a dumping ground for temporary instructions.

Ask yourselfBecomes
Who is this agent, and what does it care about more than sounding impressive?The opening two lines — identity
How should it talk when it disagrees with me?Style
What tone or habit would make me close the window?Avoid
What should it do every time, without being asked?Defaults
What must it never do, even if I ask in a hurry?Hard limits
The guide’s advice is to iterate, not to get it right first: start from a template, cut what does not apply, add four to eight lines that are actually yours, then talk to it and adjust what grates.

Give it a soul

You do not have to hunt for the file on disk — Hermes takes the soul when you create the profile. Open the profile menu at the bottom left of the sidebar and choose Manage profiles.

Bottom left of the sidebar → Manage profiles.

Create a new profile, give it a lowercase name, and paste your chosen soul into the SOUL.md field. Clone from copies config and skills from an existing profile — leave it on default for your first one.

The SOUL.md field takes the template directly. Paste, then Create profile — no file browsing.
Steps · tap the number to check0/4
  1. Open Manage profiles and create a new profile with a lowercase name.
  2. Paste a soul into the SOUL.md field. Keep project paths out of it — those belong in AGENTS.md.
  3. Create the profile, then start a session on it and ask: “Who are you and what are your hard limits?”
  4. Optional: place a short AGENTS.md in a real project folder and ask a project-specific question from that directory.
Checklist · this device0/3

You are done when

Proof · this device0/1

Stored on this device only — not sent anywhere.