agentleFS
john-data-chenjohn-data-chen/hermes-agent-backup/skills/devops/hermes-config-backup/SKILL.md

hermes-config-backup

Skill2 starsChanged 4 months agoMITView on GitHub

Backup Hermes config, skills, memories, and cron jobs. Exclude secrets. Check for info leakage before compressing.

  • Reads credentials
  • Deletes or force-pushes

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If real secrets found → redact before compressing.

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hermes Config Backup

Backup essential Hermes files. Exclude secrets and sensitive data.

What to Backup

IncludeExclude
config.yaml.env (API keys)
memories/MEMORY.mdauth.json (OAuth tokens)
memories/USER.mdstate.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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.