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 agentmods add instructions/redwoodog/hermes-desktop/testinggit clone --depth 1 https://github.com/RedWoodOG/Hermes-DesktopWhat 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 | $0.02180 | $0.02180 |
| Opus 5 | $0.01090 | $0.01090 |
| Sonnet 5 | $0.00436 | $0.00436 |
| Haiku 4.5 | $0.00218 | $0.00218 |
Grade C, and why
Hermes-Desktop testing.instructions.md scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Use latest stable versions; do not hard-code version numbers in instructions --> The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 279 lines · 2,180 tokens per session scan C c9e74497cc09
Hermes-Desktop testing.instructions.md is an instructions file published in the GitHub repository RedWoodOG/Hermes-Desktop (178 stars, last pushed 3mo ago), with no licence file. It adds 2,180 tokens to every session, about $0.0109 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
presidio recognizers.instructions.md
Instructions for data-privacy-stack/presidio, covering recognizer changes, the load-bearing rule: test the configuration path, placement and naming, pattern scores and context words.
omnigent copilot-instructions.md
Copilot instructions for omnigent-ai/omnigent, covering copilot code review instructions, e2e test requirement, backend test coverage and frontend test coverage.
Math-To-Manim tests.instructions.md
Guidelines for writing and maintaining tests in Math-To-Manim.
technocore-chat AGENTS.md
Instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
llm-ide-rules pytest-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest tests, example test and file structure.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.