Hermes Agent is an AI assistant that learns from its use by creating and improving skills, retaining knowledge, searching past conversations, and adapting to its users. It is for people who want to run an agent through a terminal or messaging platforms while connecting it to different AI models and scheduled tasks.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add NousResearch/hermes-agent --skill sherlockgit clone --depth 1 https://github.com/NousResearch/hermes-agentWrote 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/nousresearch/hermes-agent/sherlock)<a href="https://agentmods.dev/skills/nousresearch/hermes-agent/sherlock"><img src="https://agentmods.dev/badge/skills/nousresearch/hermes-agent/sherlock.svg" alt="Measured on agentmods" height="20"></a>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.00015 | $0.01436 |
| Opus 5 | $0.00008 | $0.00718 |
| Sonnet 5 | $0.00003 | $0.00287 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
sherlock 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 3d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- sherlock — 100% identical, 0 lines differ
- sherlock — 100% identical, 0 lines differ
- sherlock — 100% identical, 0 lines differ
- sherlock — 98% identical, 2 lines differ
- sherlock — 98% identical, 2 lines differ
- sherlock — 97% identical, 5 lines differ
- sherlock — 95% identical, 3 lines differ
- sherlock — 95% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sherlock OSINT Username Search
Hunt down social media accounts by username across 400+ social networks using the Sherlock Project.
When to Use
- User asks to find accounts associated with a username
- User wants to check username availability across platforms
- User is conducting OSINT or reconnaissance research
- User asks "where is this username registered?" or similar
Requirements
- Sherlock CLI installed:
pipx install sherlock-projectorpip install sherlock-project - Alternatively: Docker available (
docker run -it --rm sherlock/sherlock) - Network access to query social platforms
Procedure
1. Check if Sherlock is Installed
Before doing anything else, verify sherlock is available:
sherlock --version
If the command fails:
- Offer to install:
pipx install sherlock-project(recommended) orpip install sherlock-project - Do NOT try multiple installation methods — pick one and proceed
- If installation fails, inform the user and stop
2. Extract Username
Extract the username directly from the user's message if clearly stated.
Examples where you should NOT use clarify:
- "Find accounts for nasa" → username is
nasa - "Search for johndoe123" → username is
johndoe123 - "Check if alice exists on social media" → username is
alice - "Look up user bob on social networks" → username is
bob
Only use clarify if:
- Multiple potential usernames mentioned ("search for alice or bob")
- Ambiguous phrasing ("search for my username" without specifying)
- No username mentioned at all ("do an OSINT search")
When extracting, take the exact username as stated — preserve case, numbers, underscores, etc.
3. Build Command
Default command (use this unless user specifically requests otherwise):
sherlock --print-found --no-color "<username>" --timeout 90
Optional flags (only add if user explicitly requests):
--nsfw— Include NSFW sites (only if user asks)--tor— Route through Tor (only if user asks for anonymity)
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.
- 3d ago First seen · 193 lines · 15 tokens per session scan A 2438794f4699
sherlock is a skill published in the GitHub repository NousResearch/hermes-agent (242,093 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 1,436 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
claude-api
Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude…
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
verification-loop
A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.
options
Present multiple design options as a vertical stack of anchored turns.