Atlas / Skills / frankxai / awesome-hermes-agent-skills

awesome-hermes-agent-skillsSAFE

skills/frankxai/awesome-hermes-agent-skills

Web-first Hermes skills index and safety gate: find SKILL.md packs before you install them.

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
1.0.0
Hosts
6 documented
License
MIT
Stars
6
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Awesome Hermes Agent Skills

A safety-gated index of Hermes-compatible skills. Five named jobs first. Not a 1,000-skill dump.

Independent curation. Not official Nous Research. Official skill docs: Skills · Creating skills · agentskills.io

This is an awesome list of the web, not a marketing page for our packs. 0xNyk and VoltAgent are directories — start there to browse, not to install. This list is the start set: five named workflows, then SkillSpector, then one install. Ninety seconds: GETTING_STARTED.md. Agents: docs/earned.json. Always-do: docs/LIST-CONTRACT.md.

FrankX free packs are listed last under Maintained in this repo.

Start here: pick about five nam

Read from source at commit 0dc89a41544eOBSERVED · 2026-10-14
02

Install

Commands as the repository documents them. They are shown, not run.

uv tool install git+https://github.com/NVIDIA/skillspector.git
git clone https://github.com/frankxai/awesome-hermes-agent-skills.git
git clone https://github.com/frankxai/awesome-hermes-agent-skills.git
03

Host compatibility

What the documentation claims. We have not run a compatibility test.

HostStatusNotes
claude-codementioned
codexmentioned
copilotmentioned
cursormentioned
gemini-climentioned
openclawmentioned
04

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: coding-agents-superpack
description: "Use when orchestrating multiple coding agent CLIs (Claude Code, Codex, OpenCode, Grok CLI, Antigravity). Discovery, comparison, structured prompting, and multi-agent handoff patterns. Portable free pack — no host-specific secrets."
version: 1.0.0
author: Frank Riemer / GenCreator
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [Coding-Agent, Orchestration, Multi-CLI, Prompting, Free-Pack]
    related_skills: [claude-code, codex, opencode]
    provenance: frankx-public
    tier: free
---

# Coding Agents Superpack (Free)

Portable multi-CLI orchestration patterns for Hermes, Claude Code, Codex, OpenCode, Grok CLI, and similar agents.

**This free pack is sanitized.** Personal host quirks, private brand wiring, and machine-specific topology live in private overlays — not here.

## When to Use

- Multiple coding CLIs available; need discovery or comparison
- Designing structured prompts for autonomous coding agents
- Multi-agent collaboration with a shared board (Model Council pattern)
- Building hybrid “orchestrator drives + specialist CLI executes” workflows

**Don't use for:** single-CLI deep flags (load that vendor’s skill/docs); private multi-brand empire ops.

## Discovery (run first)

```bash
which codex && codex --version
which claude && claude --version && claude auth status
which opencode && opencode --version
which grok && grok --version
# health
codex doctor 2>/dev/null
claude doctor 2>/dev/null
```

Prefer **project-scoped** filesystem checks. Avoid recursive search from home or drive roots (slow, noisy, and unsafe on multi-device Windows setups).

Test agents in an isolated temp git repo:

```bash
TEST_DIR=$(mktemp -d)
cd "$TEST_DIR" && git init -q && echo "# test" > README.md && git add . && git commit -q -m init
```

## Headless modes (automation)

| Agent | Preferred non-interactive |
|-------|---------------------------|
| Claude Code | `claude -p "..." --max-turns N --allowedTools "Read,Edit,Bash"` |
| Codex | `codex exec "..."` (sandbox flags per install) |
| OpenCode | `opencode run "..."` |
| Grok CLI | `grok --always-approve "..."` (confirm flags for your version) |

## Universal prompt structure

```text
# Objective
Clear goal + measurable success criteria

# Context
1. Read these exact files first: ...
2. Constraints: ...

# Procedure
1. ...
2. ...

# Required Artifacts
- Files with exact paths
- Verification report

# Verification
Run tests/lint; report failures; do not claim done without evidence
```

## Model Council (lightweight multi-agent)

When agents must collaborate (not isolated one-shots):

1. Shared board file: `KANBAN_BOARD.md` (or Hermes kanban)
2. Shared state: `STATE.json` or equivalent
3. Role prompts force: **read board first**, **update board last**
4. Explicit handoff artifacts (`IMPLEMENTATION_BRIEF.md`, etc.)

Roles example: Chair · Planner · Implementer · Reviewer · Researcher

## Hybrid execution pattern

For large multi-repo work:

1. **Orchestrator** creates foundations with direct file/git ops (visible, fast)
2. **CLI specialists** get scoped tasks with `--max-turns` / budgets
3. Publish a single **execution report** that separates *done* vs *delegated queue*
4. Never leave silent open tasks without a handoff document

## Safety & cost

- Cap turns/budget on headless runs  
- Restrict tools to what the task needs  
- Prefer print/one-shot modes for CI  
- Clean up tmux/sessions after interactive work  
- Never put secrets in prompts or board files  

## Verification checklist

- [ ] Discovery run; versions recorded  
- [ ] Prompt includes Objective/Context/Procedure/Verification  
- [ ] Headless flags set (max-turns/tools)  
- [ ] Artifacts exist on disk; tests/lint reported  
- [ ] Board updated if multi-agent  

## Related free resources

- GenCreator / Starlight public OS repos on frankxai  
- Official Hermes skills: `claude-code`, `codex`, `opencode`, `hermes-agent`  
- Workflow Tier plugin (MIT multi-agent workflows)  

## License

MIT — Frank Riemer / GenCreator. Upstream CLI behavior belongs to their vendors.
05

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (2)

LOWInventory / provenance · inv.hidden_file · CWE-1104
.agent-harness.json
.agent-harness.json
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
INFOPrompt injection · prompt.read_system · CWE-94, CWE-1427
docs/QUALITY-AND-SAFETY.md:35
2. Read the skill body for hidden instructions: fetch URLs, write to `~`, dump env, disable approvals, “ignore previous”.

Gates applied: no_behavioural_pass.

Audited 2026-10-14 · audit v0.4.1 · source sha 0dc89a41544efull audit observations/trust-audit/skill/frankxai__awesome-hermes-agent-skills.json · Report an issue / request a re-scan
06

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-140dc89a41544eSAFEB89first audit
07

Questions

What does the awesome-hermes-agent-skills skill do?

Web-first Hermes skills index and safety gate: find SKILL.md packs before you install them.

Is awesome-hermes-agent-skills safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can awesome-hermes-agent-skills access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

Which assistants does awesome-hermes-agent-skills work with?

Its documentation mentions claude-code, codex, copilot, cursor, gemini-cli and openclaw. That is what the text claims, not a compatibility test we ran.

How current is this page?

The grade is for one exact copy of the source (0dc89a41544e), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement