Hermes One is a desktop application for installing, configuring, and chatting with Hermes Agent, an AI assistant that uses tools, memory, skills, scheduling, and messaging integrations. It is for people who want to manage Hermes Agent through a graphical interface, and the catalogue entries support its workflows with skills, hooks, instructions, and settings.
Borrowing it
Nothing to install: this file belongs to fathah/hermes-desktop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fathah/hermes-desktop/main/.agents/skills/lat-md/SKILL.mdgit clone --depth 1 https://github.com/fathah/hermes-desktopWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/fathah/hermes-desktop/lat-md)<a href="https://agentmods.dev/skills/fathah/hermes-desktop/lat-md"><img src="https://agentmods.dev/badge/skills/fathah/hermes-desktop/lat-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fathah/hermes-desktop/lat-md"><img src="https://agentmods.dev/badge/skills/fathah/hermes-desktop/lat-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.01094 |
| Opus 5 | $0.00021 | $0.00547 |
| Sonnet 5 | $0.00008 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
lat-md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lat.md Authoring Guide
This skill covers the syntax, structure rules, and conventions for writing lat.md/ files. Load it whenever you need to create or edit sections in the lat.md/ directory.
What belongs in lat.md
lat.md/ files describe what the project does and why — domain concepts, key design decisions, business logic, and test specifications. They do NOT duplicate source code. Think of each section as an anchor that source code references back to.
Good candidates for sections:
- Architecture decisions and their rationale
- Domain concepts and business rules
- API contracts and protocols
- Test specifications (what is tested and why)
- Non-obvious constraints or invariants
Bad candidates:
- Step-by-step code walkthroughs (the code itself is the walkthrough)
- Auto-generated API docs (use tools for that)
- Temporary notes or TODOs
Section structure
Every section must have a leading paragraph — at least one sentence immediately after the heading, before any child headings or other block content.
The first paragraph must be ≤250 characters (excluding [[wiki link]] content). This paragraph is the section's identity — it appears in search results, command output, and RAG context.
# Good Section
Brief overview of what this section documents and why it matters.
More detail can go in subsequent paragraphs, code blocks, or lists.
## Child heading
Details about this child topic.
# Bad Section
## Child heading
This is invalid — "Bad Section" has no leading paragraph.
lat check enforces this rule.
Section IDs
Sections are addressed by file path and heading chain:
- Full form:
lat.md/path/to/file#Heading#SubHeading - Short form:
file#Heading#SubHeading(when the file stem is unique)
Examples: lat.md/tests/search#RAG Replay Tests, cli#init, parser#Wiki Links.
Wiki links
Cross-reference other sections or source code with [[target]] or [[target|alias]].
Section links
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 170 lines · 42 tokens per session scan A 39c77385d424
lat-md is a skill published in the GitHub repository fathah/hermes-desktop (14,174 stars, last pushed 5d ago), licensed MIT. It adds 42 tokens to every session and 1,094 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
git-workflow
When the user asks you to perform git operations, create branches, open PRs, manage releases, or resolve conflicts, follow this guide. These are the procedural patterns you should apply consistently.
x-intelligence
When the user asks you to search, monitor, or analyze content on X (formerly Twitter), follow this guide. All operations use the official X API v2 and optionally the xAI Grok API for analysis. Never scrape. Never use unofficial endpoints.
agent_management
This Skill provides a complete management guide for OpenSquad Agents, covering the full workflow of creation, configuration, deployment, and troubleshooting.
Collaboration Management
Complete guide to multi-agent collaboration card management, including starting collaborations, joining teams, and creating custom collaboration cards.
collaboration-workflow
Complete guide to the OpenSquad multi-agent collaboration system with user authorization gates. Use this skill when starting a collaboration session, coordinating multiple agents, managing the collaboration board, or when you need to understand how to use boardupdate, boardlist, and other collaboration tools. Triggers…
mcp_auto_deploy
Allows the agent to self-configure and deploy MCP servers. Covers central config, per-agent sync, web UI visibility, registration diagnostics, and validation.