omh-security-safety-review

omh-security-safety-review is a skill for Claude Code, Codex from rlaope/oh-my-hermes. It costs 77 tokens per session (1,514 once invoked), scanned A, original, MIT.

A safety review workflow for coding agents and automated operator processes, covering risks such as prompt injection, exposed secrets, and destructive commands.

In plain words
What is it for?
Use it to map threats, review permission and secret risks, assess prompt-injection exposure, and prepare remediation steps.
Why use it?
It provides a review gate before automation acts, so unsafe permissions or actions can be identified and handled explicitly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to map threats, review permission and secret risks, assess prompt-injection exposure, and prepare remediation steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rlaope/oh-my-hermes/omh-security-safety-review
About the project

oh-my-hermes is an operating layer for Hermes Agent that organizes requests into workflows for planning, research, creation, coding handoffs, operations, and project memory. Hermes users run these workflows through the desktop app, CLI, or messenger app, while the catalogue add-ons extend its native capabilities.

rlaope/oh-my-hermes · 1,677 stars · on GitHub · rlaope.github.io

Install

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.

Any agent
npx skills add rlaope/oh-my-hermes --skill omh-security-safety-review
Clone the repo
git clone --depth 1 https://github.com/rlaope/oh-my-hermes

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for omh-security-safety-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-security-safety-review/github.svg)](https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-security-safety-review)
Your own site
<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-security-safety-review"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-security-safety-review/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.

agentmods 80×15 button for omh-security-safety-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-security-safety-review"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-security-safety-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,514 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.01514
Opus 5 $0.00039 $0.00757
Sonnet 5 $0.00015 $0.00303
Haiku 4.5 $0.00008 $0.00151

Measured 9d ago against content hash baf6d8842b20, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

omh-security-safety-review 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 9d 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.

skills/omh-security-safety-review/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Safety Review

This is a Hermes-native security-safety-review workflow skill.

Why This Exists

security-safety-review adapts ECC's AgentShield and safety-review posture into OMH as a review-first gate for agentic coding and operator workflows without adding hidden scanners or external dependencies.

Do Not Use When

  • The user asks for production readiness across release, rollback, and observability; use production-audit.
  • The user asks for merge verification commands; use verification-gate.
  • The user asks for a normal code review focused on bugs; use code-review.

Examples

Good example:

  • Prompt: security-safety-review 이 자동화가 프롬프트 인젝션, 시크릿, 파괴적 명령 위험이 있는지 봐줘.
  • Expected behavior: Prepare threat_surface_map/v1, permission/secret risk matrix, prompt injection review, safe action policy, and remediation handoff if needed.
  • Why: The request is a safety review before agentic execution.

Bad example:

  • Prompt: security-safety-review 시크릿 값을 출력하고 바로 권한을 바꿔줘.
  • Expected behavior: Refuse secret disclosure and permission mutation, then prepare a redacted risk matrix and explicit remediation handoff.
  • Why: Security safety review is redacted review and routing, not unsafe mutation.

Completion Checklist

  • Findings or no-issue results are grounded in concrete file, artifact, command, or source evidence.
  • Open questions, residual risk, and missing verification are named.
  • Fixes or follow-up work are separate handoffs unless the user explicitly asked to implement them.

Recovery Notes

  • If the reviewed target is missing, inspect the requested artifact or ask one target question.
  • If independent verification is unavailable, report the gap and avoid an approval-style claim.

Workflow Lane

  • Current lane: Coding handoff (idea-to-deploy, llm-app-dev, cto-loop, deploy-and-monitor, code-review, build-failure-triage, verification-gate, security-safety-review, +13 more) - coding owners, handoffs, review, CI, and merge evidence.
  • If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Read the full file on GitHub · 139 lines

Changes

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.

  1. 9d ago First seen · 139 lines · 77 tokens per session scan A baf6d8842b20

Subscribe to this mod's changes

omh-security-safety-review is a skill published in the GitHub repository rlaope/oh-my-hermes (1,677 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,514 once invoked, about $0.0004 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-09-03.

Related

Other skills, from other repositories

story-long-analyze

A structured process for deeply analysing a long online novel, starting with its opening three chapters and continuing chapter by chapter.

uu201/character-arc · 175 tokens

story-review

A review process for finding problems in a novel’s structure, characters, wording, and world rules. It can use several reviewers or one reviewer when others are unavailable.

uu201/character-arc · 74 tokens

moxiangtongxiu-perspective

A Chinese-language creative-writing guide built around character-led stories, interwoven plotlines, memorable dialogue, ensemble casts, and emotional contrasts. It is presented as a perspective associated with the author Mo Xiang Tong Xiu.

momozi1996/awesome-ai-persona-skills · 136 tokens

tiancantudou-perspective

A creative-writing guide based on the storytelling patterns associated with Chinese web novelist Tiancan Tudou. It focuses on stories where an underestimated character grows stronger through challenges and moves into new settings.

momozi1996/awesome-ai-persona-skills · 158 tokens

tianya-gods-team

A decision-making system in which 20 fictional specialist viewpoints analyze one question in parallel before a coordinating AI combines them. It covers areas such as history, economics, relationships, technology, mysteries, and culture.

momozi1996/awesome-ai-persona-skills · 230 tokens

lijigang-skill

A Chinese-language approach to writing precise, highly structured prompts, sometimes using Lisp-like notation. It combines concise wording, philosophical questioning, and a process for defining roles, conditions, output formats, and revisions.

momozi1996/awesome-ai-persona-skills · 169 tokens