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 skillmds/skillmd --skill cli-anything-hermesgit clone --depth 1 https://github.com/skillmds/skillmdWrote 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/skillmds/skillmd/cli-anything-hermes)<a href="https://agentmods.dev/skills/skillmds/skillmd/cli-anything-hermes"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/cli-anything-hermes/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/skillmds/skillmd/cli-anything-hermes"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/cli-anything-hermes.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.01018 |
| Opus 5.5 | $0.00021 | $0.00407 |
| Sonnet 5 | $0.00011 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
cli-anything-hermes 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 4d 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.
This is a copy
100% identical to cli-anything-hermes — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI-Anything for Hermes Agent
Use this skill when the user wants Hermes Agent to act like the CLI-Anything builder.
Before implementation, use the full methodology source of truth when available:
- If this skill is being used from inside the
CLI-Anythingrepository, read../cli-anything-plugin/HARNESS.mdfirst. - If that local file is unavailable, clone or download
cli-anything-pluginfromhttps://github.com/HKUDS/CLI-Anything/tree/main/cli-anything-plugin, then useHARNESS.mdand the resources around it from that folder. - Only if both local and network retrieval fail, follow the condensed rules below.
Inputs
Accept either:
- A local source path such as
./gimpor/path/to/software - A GitHub repository URL
Derive the software name from the local directory name after cloning if needed.
Hermes Tool Bindings
Hermes agents build harnesses by combining these built-in tools:
| Tool | Role in Harness Workflow |
|---|---|
terminal |
Run shell commands, install packages, execute CLI tools, run tests |
execute_code |
Generate and write Python files (Click CLI, backend modules, tests) |
delegate_task |
Parallelize analysis or generation subtasks |
read_file / write_file |
Read and write harness source files |
patch |
Make targeted edits to generated code |
Consult the Hermes Agent documentation for the exact tool invocation syntax.
Modes
Build
Use when the user wants a new harness.
Produce this structure:
<software>/
└── agent-harness/
├── <SOFTWARE>.md
├── setup.py
└── cli_anything/
└── <software>/
├── README.md
├── __init__.py
├── __main__.py
├── <software>_cli.py
├── core/
├── utils/
└── tests/
Implement a stateful Click CLI with:
- one-shot subcommands
- REPL mode as the default when no subcommand is given
--jsonmachine-readable output- session state with undo/redo where the target software supports it
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.
- 4d ago First seen · 134 lines · 53 tokens per session scan A ddafc25ce3b7
cli-anything-hermes is a skill published in the GitHub repository skillmds/skillmd (1 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,018 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cli-anything-hermes, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
slopless
Use Slopless to review English Markdown for deterministic AI and human slop signals, including vague phrasing, formulaic prose, weak rhythm, filler, and cliches.
suiko
A Japanese writing and review workflow for checking whether text sounds uniform, translated, unnatural, or difficult to read. It supports writing and editing documents such as reports, guides, meeting notes, proposals, and emails.
poly-lint-and-format
Running poly lint / poly fmt — --fix, --format pretty|json|toon, --exclude, --config, exit codes, inline suppression, and the check → read-json → fix → re-check loop.
poly-orchestrator
Use poly as the single lint/format gate instead of invoking ruff/oxlint/rustfmt directly — one poly.toml, poly hooks install, poly migrate, CI via the Goldziher/poly setup Action.
poly-mcp
The poly MCP server — the eleven tools and which are read-only vs mutating, the paths/exclude/config/format params, async Tasks for the whole-project phase, and the isError contract.
poly-tiers-and-scope
Five mechanisms decide what actually inspects a file (crates/poly-core/src/registry.rs).