Hermes Agent for Torn City
I have been playing around with Hermes Agent as a personal Torn assistant. It turned out to be more useful than I expected, so I wanted to share the basic idea.
This is not about making a bot that plays Torn for you. Please do not do that.
The useful part is having a private assistant you can ask questions to. It can explain game mechanics, keep notes, help you understand API data, and help you build small read-only tools around your own account.
1. What is Hermes, and why would you use it?
Hermes Agent is an open-source AI agent that runs on your computer. You can use it in the terminal, or connect it to Telegram / WhatsApp if you prefer asking things from your phone.
For Torn, that means you can use it as a personal helper for stuff like:
- understanding Torn mechanics without digging through ten tabs
- building a small Torn knowledge base for yourself
- asking beginner or intermediate gameplay questions
- looking up Torn API or FFScouter API information
- saving reusable notes, prompts, skills, and helper scripts
- using the same setup from desktop or mobile
The main trick is to stop treating AI like a one-shot Q&A box.
Ask it to build the knowledge first, then ask it to build the system that uses that knowledge.
That is where it starts becoming genuinely useful.
2. Installation
Install Hermes, check HERE the command, then run the setup wizard:
hermes setup
Check that the install looks healthy:
hermes doctor
hermes config
Pick your model/provider and enable the tools you want:
hermes model
hermes tools
For a Torn setup, I would start with these tools:
- web, for checking current info when needed
- skills, for reusable Torn knowledge and workflows
- memory, for stable personal preferences and context
- session_search, for finding things you already discussed
- terminal/file, if you want Hermes to create local notes or helper scripts
After changing tools, start a fresh Hermes session so the new tool list is loaded.
3. Optional Telegram / WhatsApp setup
You can keep Hermes terminal-only if you want. That is the simplest version.
If you want to ask Torn questions from your phone, set up the gateway:
hermes gateway setup
hermes gateway run
4. Make it Torn-related
Do this in stages. If you ask for everything in one giant prompt, the result usually gets messy.
These prompts split the work into clean pieces:
Prompt 1: build the gameplay knowledge
You are helping me build a Torn City gameplay knowledge base for Hermes Agent.
Create compact, reusable knowledge for answering Torn player questions.
Cover:
- beginner priorities
- energy, nerve, happiness, cooldowns, and gym training
- crimes 2.0
- travel and basic money-making
- factions and organized crime basics
- missions, education, merits, and common terminology
Rules:
- explain gameplay, do not write code
- keep each topic short and easy to search
- include beginner mistakes and traps
- summarize sources instead of copying large blocks of text
- separate stable game concepts from advice that might change later
Output:
- a proposed folder/file structure
- the first version of the knowledge base
- a list of topics to verify or update later
Prompt 2: build the API helper
You are helping me create a Torn API helper for Hermes Agent.
Build a simple, legal, read-only helper setup for Torn API and FFScouter API.
Requirements:
- keep API/helper code separate from gameplay knowledge
- use a .env file next to the helper script
- explain that I should put these keys in that .env file:
TORN_API_KEY=your_key_here
FFSCOUTER_API_KEY=your_key_here
- support basic endpoint lookup
- support live API requests that return JSON
- include examples for user info, bars/resources, and FFScouter stats if available
- do not create automation that plays Torn or breaks Torn/API rules
Output:
- recommended folder structure
- helper script design
- .env example
- example commands
- safety notes and limitations
Prompt 3: turn it into Hermes skills
Turn my Torn gameplay knowledge and Torn API helper design into reusable Hermes Agent skills.
Create two separate skills:
1. Torn gameplay knowledge skill
2. Torn API / FFScouter reference skill
For each skill, include:
- when Hermes should load it
- what questions it should answer
- what files or references it should use
- common pitfalls
- verification steps
Keep gameplay advice in the gameplay skill.
Keep endpoints, helper usage, and technical lookups in the API skill.
Prompt 4: connect the whole assistant
Help me connect my Torn Hermes setup into a usable assistant.
Use the Torn gameplay skill for gameplay questions.
Use the Torn API / FFScouter skill for endpoint lookup and live data questions.
Use the API helper only when live data is actually needed.
Create:
- a simple daily-use workflow
- example questions I can ask
- a checklist to test that the setup works
- a maintenance workflow for updating the knowledge base and API reference
- instructions for using it from terminal, Telegram, or WhatsApp
Keep it simple enough that a normal Torn player can follow it.
Prompt 5: add a rules / responsible-use section
Add a short responsible-use section for this Torn Hermes setup.
Make it clear that the assistant is for learning, notes, explanations, and legal helper tools.
It should not be used for automated gameplay, spam, scraping abuse, botting, or anything that violates Torn rules or API rules.
Keep the warning short and suitable for a Torn forum post.
5. API helper: where the keys go
If you build the API helper, put the keys in a .env file next to the helper script. Keep it boring and obvious.
TORN_API_KEY=your_key_here
FFSCOUTER_API_KEY=your_key_here
The helper reads that file when it makes API requests. If a key leaks or you want to replace it, change it in .env and restart whatever is using the helper.
6. Examples of things you can ask
- What should a new Torn player focus on first?
- Explain energy, nerve, and happiness like I am new.
- What are common beginner mistakes in Torn?
- How should I think about training versus money-making?
- Which Torn API endpoint gives my current bars?
- Help me design a small Torn tracker that only reads API data.
- Turn my Torn notes into a reusable Hermes skill.
7. What you can build after that
- a personal Torn FAQ assistant
- a beginner guide helper
- a faction knowledge base
- travel and money-making notes
- an API lookup assistant
- a Telegram or WhatsApp Torn companion
- read-only dashboards and trackers
- a personal strategy notebook
Start small. Build the knowledge, build the helper, turn both into reusable skills, then improve the setup as you actually use it.
Final note
Use this responsibly. Hermes is great for learning Torn, organizing information, understanding API data, and building legal helper tools.
It should not be used for botting, spam, automated gameplay, or anything that breaks Torn rules.
The more you keep the knowledge clean and updated, the more useful the assistant gets.