Install
$ agentstack add skill-john-data-chen-hermes-agent-backup-hermes-config-backup ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Hermes Config Backup
Backup essential Hermes files. Exclude secrets and sensitive data.
What to Backup
| Include | Exclude | |---------|---------| | config.yaml | .env (API keys) | | memories/MEMORY.md | auth.json (OAuth tokens) | | memories/USER.md | state.db (session store) | | skills/ (all) | sessions/ (transcripts) | | cron/jobs.json | *.lock (0-byte) | | | hermes-agent/ (source) | | | logs/, cache/, audio_cache/, image_cache/ | | | .DS_Store |
Workflow
1. Prepare temp directory
BACKUP_DIR="/tmp/hermes-backup-$(date +%Y%m%d_%H%M%S)"
mkdir -p "$BACKUP_DIR"
cd ~/.hermes
2. Copy files
cp config.yaml "$BACKUP_DIR/"
mkdir -p "$BACKUP_DIR/memories"
cp memories/MEMORY.md memories/USER.md "$BACKUP_DIR/memories/"
mkdir -p "$BACKUP_DIR/skills"
rsync -a --exclude='*.lock' --exclude='.DS_Store' --exclude='node_modules' skills/ "$BACKUP_DIR/skills/"
mkdir -p "$BACKUP_DIR/cron"
cp cron/jobs.json "$BACKUP_DIR/cron/"
3. Check for info leakage
Before compressing, scan for sensitive data:
# API keys (non-empty)
grep -rE 'api_key:\s*[^'\'']' "$BACKUP_DIR/" | grep -v node_modules
# Tokens
grep -rE 'ghp_|gho_|github_pat_|sk-[a-zA-Z0-9]{20,}' "$BACKUP_DIR/" | grep -v node_modules | grep -v 'example\|sample\|xxx'
# Phone numbers (exclude numeric config values)
grep -rE '\+?[0-9]{1,4}[-.\s]?\(?\d{1,4}\)?[-.\s]?\d{1,4}[-.\s]?\d{1,4}[-.\s]?\d{1,9}' "$BACKUP_DIR/" | grep -v 'timeout\|limit\|max\|min\|bytes\|chars\|sample_rate\|bit_rate'
# Email addresses
grep -rE '[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}' "$BACKUP_DIR/"
If real secrets found → redact before compressing.
4. Compress as zip
ZIP_FILE="$HOME/backups/hermes/hermes-backup-$(date +%Y%m%d_%H%M%S).zip"
mkdir -p "$(dirname "$ZIP_FILE")"
cd "$BACKUP_DIR" && zip -r "$ZIP_FILE" . -x '*.DS_Store'
5. Cleanup
rm -rf "$BACKUP_DIR"
Pitfalls
> Never include .env or auth.json. These contain API keys and OAuth tokens.
> Always check for info leakage. Even config.yaml may contain API URLs or voice IDs. Mask if needed.
> **Exclude .lock files.* They are 0-byte and not needed.
> Use zip format. Not tar.gz.
> Backup path: ~/backups/hermes/hermes-backup-YYYYMMDD_HHMMSS.zip
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: john-data-chen
- Source: john-data-chen/hermes-agent-backup
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.