Hermes BibleUnofficial Docs
← All flows Flow / Configuration

Hermes Agent SOUL.md: Why 50 Lines Matter More Than Your Model

A complete guide to SOUL.md — where it sits in the prompt stack, what belongs in it, token economics, advanced role templates, /personality overlays, profiles, and the iterative method for growing an effective agent identity.

Hermes AgentSOUL.mdsoul.mdlinesmattermodelwherepromptstack
Category
Configuration
Level
Community
Author
YanXbt
Reading time
5 min

A complete guide to SOUL.md — where it sits in the prompt stack, what belongs in it, token economics, advanced role templates, /personality overlays, profiles, and the iterative method for growing an effecti...

Community flow by YanXbt. View source

Flow sections

Section outline mirrored from the public community flow. Use the source page for full prose and examples.

Upstream outline

  1. 1. What SOUL.md Actually Is
  2. 2. Where SOUL.md Sits in the Prompt Stack
  3. 3. The Rules: What Goes In and What Does Not
  4. Voice
  5. Restrictions
  6. The injection scanner
  7. 4. Token Impact
  8. 5. The Structure That Works
  9. Voice
  10. Operations
  11. Restrictions
  12. Style
  13. Avoid
  14. 6. Advanced SOUL.md Templates

Section map

1. What SOUL.md Actually Is

Frames 1. what soul.md actually is for this Configuration workflow, including the operating context to verify in the source page.

2. Where SOUL.md Sits in the Prompt Stack

Frames 2. where soul.md sits in the prompt stack for this Configuration workflow, including the operating context to verify in the source page.

3. The Rules: What Goes In and What Does Not

Frames 3. the rules: what goes in and what does not for this Configuration workflow, including the operating context to verify in the source page.

Voice

Frames voice for this Configuration workflow, including the operating context to verify in the source page.

Restrictions

Frames restrictions for this Configuration workflow, including the operating context to verify in the source page.

The injection scanner

Frames the injection scanner for this Configuration workflow, including the operating context to verify in the source page.

4. Token Impact

Frames 4. token impact for this Configuration workflow, including the operating context to verify in the source page.

5. The Structure That Works

Frames 5. the structure that works for this Configuration workflow, including the operating context to verify in the source page.

Implementation notes

  • Use this Configuration flow as a pattern library entry: start from the summary, then inspect the linked source before copying any commands, schedules, or account wiring.
  • Primary decision areas: 1. What SOUL.md Actually Is, 2. Where SOUL.md Sits in the Prompt Stack, 3. The Rules: What Goes In and What Does Not, Voice, Restrictions. Treat those sections as checkpoints for scope, cost, orchestration, and human review.
  • Useful search signals for this flow: soul.md, lines, matter, model, where. These are derived from the public title and summary, not from private runtime data.

Decision table

Best fitConfiguration workflow pattern

Use when the summary outcome matches your own workflow and 1. what soul.md actually is is relevant to your setup.

Verify firstAccounts, models, schedules, and tool access

Open the source sections for 1. What SOUL.md Actually Is and 2. Where SOUL.md Sits in the Prompt Stack before wiring credentials or automation.

Review boundaryHuman approval point

Keep human approval for merges, spending, external messages, credentials, and unattended execution.

Verification checklist

  1. Confirm the workflow outcome matches your use case: A complete guide to SOUL.md — where it sits in the prompt stack, what belongs in it, token economics, advanced role templates, /personality overlays, profiles, and the iterative method for growing an effective agent identity.
  2. Open the source section for 1. What SOUL.md Actually Is before copying commands, prompts, or schedules.
  3. List every credential, account, model, and external service the flow would touch.
  4. Define the human approval step before spending money, sending messages, trading, merging, or running unattended.
  5. Run a small dry run and compare the result with the source sections for 1. What SOUL.md Actually Is and 2. Where SOUL.md Sits in the Prompt Stack.

Risk notes

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • A complete guide to SOUL.md
  • where it sits in the prompt stack, what belongs in it, token economics, advanced role templates, /personality overlays, profiles
  • the iterative method for growing an effective agent identity.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page