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 hermoso-ai/hermoso --skill hermoso-researchgit clone --depth 1 https://github.com/hermoso-ai/hermosoWrote 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/hermoso-ai/hermoso/hermoso-research)<a href="https://agentmods.dev/skills/hermoso-ai/hermoso/hermoso-research"><img src="https://agentmods.dev/badge/skills/hermoso-ai/hermoso/hermoso-research/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/hermoso-ai/hermoso/hermoso-research"><img src="https://agentmods.dev/badge/skills/hermoso-ai/hermoso/hermoso-research.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.00103 | $0.00598 |
| Opus 5 | $0.00051 | $0.00299 |
| Sonnet 5 | $0.00021 | $0.00120 |
| Haiku 4.5 | $0.00010 | $0.00060 |
Grade A, and why
hermoso-research 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 10d 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.
What it actually says
Hermoso — competitor & ad research
This is Hermoso's discovery half (which most generators don't have). Drive the Hermoso CLI.
Setup
hermoso auth login(opens your browser once; nothing to paste). On a machine with no browser:hermoso auth login --token <your key>, using a key from the app under MCP & CLI.. No account at all? An agent can sign itself up on a paid plan withPOST /v1/signupat app.hermoso.ai, no browser needed; see the Hermoso README.
Procedure
Pick the tool that fits the ask:
- Find competitors for a domain:
hermoso competitors <domain> [--mode competitors|inspiration|company] --jsoncompetitors= head-to-head rivals;inspiration= best relevant ads incl. the brand itself;company= the company's own.
- Pull a brand's real ads across ad libraries:
hermoso ads pull --company "<name>" [--domain <d>] [--platforms facebook,google,linkedin] [--country US] --json- Defaults to Meta (richest library). Add google/linkedin only if asked (Google detailed pulls cost more).
- Natural-language research (Claude tool-use over ad libraries + organic TikTok):
hermoso research "<request>"- e.g.
hermoso research "the longest-running protein-pancake ads on Meta and what hooks they use". Prints a summary + the found ads with their URLs.
- e.g.
- Synthesize: report the strongest hooks, angles, formats, and what's worth copying — be specific (quote the actual headlines/angles). If the user then wants to build one, hand off to
hermoso-ad-from-brand/hermoso-generate.
Notes
- Research spends credits (ad-library calls); keep platform scope to what's asked.
- Add
--jsonfor the raw ad objects (URLs, copy, run dates) when the user wants the data, not a summary.
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.
- 10d ago First seen · 32 lines · 103 tokens per session scan A ba63a1ac2540
hermoso-research is a skill published in the GitHub repository hermoso-ai/hermoso (0 stars, last pushed 3d ago), licensed MIT. It adds 103 tokens to every session and 598 once invoked, about $0.0005 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.