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 mergisi/awesome-hermes-agent --skill github-issue-triagegit clone --depth 1 https://github.com/mergisi/awesome-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/mergisi/awesome-hermes-agent/github-issue-triage)<a href="https://agentmods.dev/skills/mergisi/awesome-hermes-agent/github-issue-triage"><img src="https://agentmods.dev/badge/skills/mergisi/awesome-hermes-agent/github-issue-triage.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.00036 | $0.00994 |
| Opus 5 | $0.00018 | $0.00497 |
| Sonnet 5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
github-issue-triage 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Triage
Triage incoming GitHub issues so a solo maintainer's inbox doesn't explode. This skill labels new issues, asks for reproduction steps when they're missing, and closes duplicates with a link to the canonical thread.
What this skill does
For every new issue in a repository:
- Read the issue body — title, description, any code blocks, version mentioned, OS/runtime mentioned.
- Classify by type — apply one of:
bug,feature-request,docs,question,support,spam. Use the existing labels on the repo if they exist; don't invent new label names. - Estimate priority — if the issue mentions data loss, security, crashes, or production blockage →
priority-high. If it mentions a minor visual glitch or a "nice to have" →priority-low. Default →priority-medium. - Check for duplicates — search the last 90 days of closed and open issues for similar titles or error messages. If a duplicate exists, post a comment linking the canonical thread and close the new issue (only if confidence is high).
- Ask for repro — for any
buglabel without clear reproduction steps (steps, expected, actual, version), post a comment asking for them in plain language. - Spam detection — if the issue is single-line marketing, has no relevance to the repo, or is from a brand-new account with a generic title →
spamlabel and close.
What this skill does NOT do
- It does not auto-merge or auto-fix issues.
- It does not assign issues to specific maintainers.
- It does not reply with code suggestions — only labels, classification, repro requests, and dup-closes.
- It does not auto-close stale issues. Use a separate stale-bot for that.
How to invoke
Default trigger is the GitHub issues.opened webhook. Configure via hermes webhook list. For manual run on a single issue:
/github-issue-triage owner/repo#42
Configuration
In your agent config or skill metadata:
github:
default_repo: "owner/repo"
labels:
bug: "bug"
feature: "enhancement"
docs: "documentation"
spam: "spam"
dup_search_days: 90
spam_threshold: 0.85
ask_repro_template: |
Thanks for opening this. To reproduce on our end, can you share:
- The version of {project} you're on
- Steps to reproduce (1, 2, 3...)
- What you expected vs what actually happened
- Your OS / runtime if relevant
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.
- 7d ago First seen · 85 lines · 36 tokens per session scan A dbe7b3c92aba
github-issue-triage is a skill published in the GitHub repository mergisi/awesome-hermes-agent (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 994 once invoked, about $0.0002 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
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
interpreting-mod-author-instructions
A guide for following a Bethesda mod author's installation instructions, including file choices, prerequisites, and installer options.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
using-bgs-archive
Use when the user wants to inspect, list, extract, unpack, or repack Bethesda BA2/BSA archives; determine archive format/version/compression; or build archive assets for an MO2 overlay. Triggers - "unpack BA2", "extract BSA", "pack archive", "inspect archive", "bgs-archive".
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
laravel-security
Laravel security best practices for authn/authz, validation, CSRF, mass assignment, file uploads, secrets, rate limiting, and secure deployment.