agent-hardening

Detect and defend Hermes Agent against prompt injection and related threats.

13|2|Updated Mar 17, 2026

Search Tags:#security #owasp #audit #memory #hardening #unicode #prompt-injection

Ready to run

npx skills add https://github.com/amanning3390/hermeshub --skill agent-hardening

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-hardening
Source: https://github.com/amanning3390/hermeshub/tree/main/skills/agent-hardening
Command: npx skills add https://github.com/amanning3390/hermeshub --skill agent-hardening

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive security hardening for Hermes Agent. Detects prompt injection, unicode smuggling, hidden directives, supply-chain poisoning, credential exposure, and memory manipulation. Provides runtime scanning rules, input/output validation patterns, and a defense-in-depth checklist aligned with OWASP LLM Top 10.

Core Features & Use Cases

Threat detection and defense-in-depth coverage for Hermes Agent against prompt-injection, Unicode abuse, hidden directives, and memory manipulation.
Runtime scanning rules and input/output validation to prevent data leakage and memory tampering during skill processing.
Provides a structured defense checklist aligned with OWASP LLM Top 10; suitable for pre-install reviews and periodic audits.

Quick Start

Audit your Hermes Agent setup to identify and mitigate prompt-injection, memory, and supply-chain risks.

Frequently Asked Questions about agent-hardening

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I secure an LLM agent against prompt injection and memory manipulation?▼

To secure an LLM agent against prompt injection and memory manipulation, apply runtime scanning rules, input/output validation patterns, and a defense-in-depth checklist aligned with the OWASP LLM Top 10 to detect and block hidden directives and memory tampering.

What is unicode smuggling in LLM security and how is it detected?▼

Unicode smuggling in LLM security is an attack vector using hidden or manipulated characters to embed malicious directives. It is detected by applying runtime input validation patterns and scanning rules during external content processing to identify and block suspicious character payloads.

How do I audit agent memory and prompts for supply-chain poisoning?▼

To audit agent memory and prompts for supply-chain poisoning, execute periodic security audits using a structured defense checklist. This process scans ongoing agent memory and third-party skill reviews to detect credential exposure, hidden directives, and memory manipulation vulnerabilities.

Does this agent hardening approach protect against credential exposure during runtime processing?▼

Yes, this agent hardening approach protects against credential exposure during runtime processing by applying strict input/output validation patterns. These rules scan external content and third-party skill executions to prevent data leakage and identify exposed credentials.

When should I apply OWASP LLM Top 10 security checks to my agent?▼

You should apply OWASP LLM Top 10 security checks during third-party skill reviews, runtime processing of external content, and ongoing periodic security audits. This ensures continuous defense-in-depth coverage against evolving prompt injection and supply-chain threats.