Who it is forAn operator with several Bots who wants the same rules on each one, such as no spending without asking, without copying text into every SOUL.md.
The problemRules pasted into many SOUL.md files drift apart over time and are hard to keep consistent.
The outcomeOne edited policy file reaches each Bot, and stale Bots are listed so you can refresh them.
What you need first
- Hermes Agent 0.21 or newer with the hermes CLI on your PATH
- Hermes Desktop for Bot Mode (the CLI also works, since Bots are profiles)
- Linux or macOS (Windows is not supported)
- A model provider configured in Hermes
Steps
- Run
$EDITOR ~/.hermes/shared/BOT-POLICY.mdand edit the shared policy - Run
check_policiesto list which Bots are stale or opted out - Run
update_agentwithrefresh_shared_policy: truefor each stale Bot - Run
check_policiesagain to confirm no Bot is listed as stale
Prompt for your agent
Using the repo BkashJEE/hermes-bot-forge, edit ~/.hermes/shared/BOT-POLICY.md and then run check_policies. Expected output: a list of stale Bots and Bots that opted out with no_shared_policy. Verify by refreshing one stale Bot with update_agent and confirming it no longer appears in the stale list.
Caveat. The policy is prompt text the model is asked to follow, not enforced, so nothing blocks a tool call that breaks a rule.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page