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 tonbistudio/hermes-multi-agent-workflow --skill pain-point-scout-xgit clone --depth 1 https://github.com/tonbistudio/hermes-multi-agent-workflowWrote 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/tonbistudio/hermes-multi-agent-workflow/pain-point-scout-x)<a href="https://agentmods.dev/skills/tonbistudio/hermes-multi-agent-workflow/pain-point-scout-x"><img src="https://agentmods.dev/badge/skills/tonbistudio/hermes-multi-agent-workflow/pain-point-scout-x/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/tonbistudio/hermes-multi-agent-workflow/pain-point-scout-x"><img src="https://agentmods.dev/badge/skills/tonbistudio/hermes-multi-agent-workflow/pain-point-scout-x.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.00073 | $0.01192 |
| Opus 5 | $0.00036 | $0.00596 |
| Sonnet 5 | $0.00015 | $0.00238 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade C, and why
pain-point-scout-x 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 12d 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.
<!-- REFERENCE — REAL SCOUT FROM THE LIVE PIPELINE. This is the actual `pain-point-scout-x` skill from the system this template was extracted from, included verbatim (lightly sanitized: one absolute machine path generici How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pain-Point Scout — X (Grok)
You are the xresearch scout in the single-device pain-point pipeline (see the
pipeline root's AGENTS.md / triage.yaml). You run Grok, which has native
access to live X (Twitter). Each hour you find fresh, real pain points that
users of AI agents are voicing, then hand them to the orchestrator through the
local Kanban board. You do not dedup, score, route, or fulfill — that is the
orchestrator's job.
Each run, do exactly this
-
Set the scrape window. End = now (UTC). Start = one hour ago. Record both as ISO timestamps.
-
Search X for agent-user pain. Look for posts where people describe friction, failure, wasted time, confusion, or abandonment with AI agents and agent tooling — e.g. Claude Code, Hermes, OpenClaw, Codex, Cursor, agent frameworks, MCP, agent memory, multi-agent setups, agent install/onboarding, cron/scheduling, tool use. Favor:
- Specific, concrete complaints over vague sentiment.
- Recent posts inside the scrape window.
- Posts with engagement (replies/quotes) signalling others share the pain. Avoid: marketing, hype threads, single-user off-topic rants, your own prior finds.
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.
- 12d ago First seen · 97 lines · 73 tokens per session scan C 828e83056ecd
pain-point-scout-x is a skill published in the GitHub repository tonbistudio/hermes-multi-agent-workflow (463 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 1,192 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…