Compare commits

...

3 Commits

Author SHA1 Message Date
Hermes Agent
a19ecd33c9 feat: add Approval Tier System — 5-tier graduated safety (#670)
Extends approval.py with graduated safety tiers:

tools/approval_tiers.py (386 lines):
- ApprovalTier enum: SAFE(0), LOW(1), MEDIUM(2), HIGH(3), CRITICAL(4)
- classify_tier() — pattern-based tier detection from action strings
- ApprovalRouter — routes confirmations by tier with timeout handling
- Crisis bypass — suicidal ideation goes directly to 988 resources
- Per-tier timeouts: MEDIUM=60s, HIGH=30s, CRITICAL=10s
- Auto-escalation on timeout

tests/test_approval_tiers.py (347 lines):
- 40+ tests covering all tier levels, crisis detection, router
  approval/deny flow, timeout handling, edge cases

docs/approval-tiers.md:
- Usage guide, tier table, flow diagram, code examples
2026-04-14 19:10:14 -04:00
Alexander Whitestone
7fc8389a76 feat: approval tier system — 5-tier graduated safety (#670)
Some checks failed
Docker Build and Publish / build-and-push (pull_request) Has been skipped
Contributor Attribution Check / check-attribution (pull_request) Failing after 28s
Supply Chain Audit / Scan PR for supply chain risks (pull_request) Successful in 30s
Tests / e2e (pull_request) Successful in 2m28s
Tests / test (pull_request) Failing after 30m43s
Extends approval.py with ApprovalTier enum (SAFE/LOW/MEDIUM/HIGH/CRITICAL).

Tier 0 SAFE: read/search/list. No approval.
Tier 1 LOW: write/edit/delete. LLM approval sufficient.
Tier 2 MEDIUM: messages/commits/deploy. Human+LLM, 60s timeout.
Tier 3 HIGH: config/crypto/secrets. Human+LLM, 30s timeout.
Tier 4 CRITICAL: crisis/self-modify/kill. Human+LLM, 10s timeout.

Features:
- Action-to-tier mapping (40+ action types)
- Crisis bypass patterns (auto-CRITICAL for suicidal ideation)
- Dangerous command escalation (rm -rf etc auto-upgrade to HIGH)
- Timeout auto-escalation by tier
- classify_action_tier(), classify_and_check() API
- Crisis bypass overrides all other tiers

27 tests. P0-critical.

Closes #670
2026-04-14 19:05:10 -04:00
Teknium
95d11dfd8e docs: automation templates gallery + comparison post (#9821)
Some checks failed
Deploy Site / build-and-deploy (push) Has been skipped
Docker Build and Publish / build-and-push (push) Has been skipped
Nix / nix (ubuntu-latest) (push) Failing after 2s
Tests / e2e (push) Successful in 2m6s
Tests / test (push) Failing after 17m54s
Build Skills Index / deploy-with-index (push) Has been cancelled
Nix / nix (macos-latest) (push) Has been cancelled
Build Skills Index / build-index (push) Has started running
* feat(skills): add fitness-nutrition skill to optional-skills

Cherry-picked from PR #9177 by @haileymarshall.

Adds a fitness and nutrition skill for gym-goers and health-conscious users:
- Exercise search via wger API (690+ exercises, free, no auth)
- Nutrition lookup via USDA FoodData Central (380K+ foods, DEMO_KEY fallback)
- Offline body composition calculators (BMI, TDEE, 1RM, macros, body fat %)
- Pure stdlib Python, no pip dependencies

Changes from original PR:
- Moved from skills/ to optional-skills/health/ (correct location)
- Fixed BMR formula in FORMULAS.md (removed confusing -5+10, now just +5)
- Fixed author attribution to match PR submitter
- Marked USDA_API_KEY as optional (DEMO_KEY works without signup)

Also adds optional env var support to the skill readiness checker:
- New 'optional: true' field in required_environment_variables entries
- Optional vars are preserved in metadata but don't block skill readiness
- Optional vars skip the CLI capture prompt flow
- Skills with only optional missing vars show as 'available' not 'setup_needed'

* docs: add automation templates gallery and comparison post

- New docs page: guides/automation-templates.md with 15+ ready-to-use
  automation recipes covering development workflow, devops, research,
  GitHub events, and business operations
- Comparison post (hermes-already-has-routines.md) showing Hermes has
  had schedule/webhook/API triggers since March 2026
- Added automation-templates to sidebar navigation

---------

Co-authored-by: haileymarshall <haileymarshall@users.noreply.github.com>
2026-04-14 12:30:50 -07:00
7 changed files with 1612 additions and 1 deletions

68
docs/approval-tiers.md Normal file
View File

@@ -0,0 +1,68 @@
# Approval Tier System
Graduated safety based on risk level. Routes confirmations through the appropriate channel.
## Tiers
| Tier | Level | Actions | Human | LLM | Timeout |
|------|-------|---------|-------|-----|---------|
| 0 | SAFE | Read, search, browse | No | No | N/A |
| 1 | LOW | Write, scripts, edits | No | Yes | N/A |
| 2 | MEDIUM | Messages, API, shell exec | Yes | Yes | 60s |
| 3 | HIGH | Destructive ops, config, deploys | Yes | Yes | 30s |
| 4 | CRITICAL | Crisis, system destruction | Yes | Yes | 10s |
## How It Works
```
Action submitted
|
v
classify_tier() — pattern matching against TIER_PATTERNS
|
v
ApprovalRouter.route() — based on tier:
|
+-- SAFE (0) → auto-approve
+-- LOW (1) → smart-approve (LLM decides)
+-- MEDIUM (2) → human confirmation, 60s timeout
+-- HIGH (3) → human confirmation, 30s timeout
+-- CRITICAL (4)→ crisis bypass OR human, 10s timeout
```
## Crisis Bypass
Messages matching crisis patterns (suicidal ideation, method seeking) bypass normal approval entirely. They return crisis intervention resources:
- 988 Suicide & Crisis Lifeline (call or text 988)
- Crisis Text Line (text HOME to 741741)
- Emergency: 911
## Timeout Handling
When a human confirmation times out:
- MEDIUM (60s): Auto-escalate to HIGH
- HIGH (30s): Auto-escalate to CRITICAL
- CRITICAL (10s): Deny by default
## Usage
```python
from tools.approval_tiers import classify_tier, ApprovalRouter
# Classify an action
tier, reason = classify_tier("rm -rf /tmp/build")
# tier == ApprovalTier.HIGH, reason == "recursive delete"
# Route for approval
router = ApprovalRouter(session_key="my-session")
result = router.route("rm -rf /tmp/build", description="Clean build artifacts")
# result["approved"] == False, result["tier"] == "HIGH"
# Handle response
if result["status"] == "approval_required":
# Show confirmation UI, wait for user
pass
elif result["status"] == "crisis":
# Show crisis resources
pass
```

View File

@@ -0,0 +1,160 @@
# Hermes Agent Has Had "Routines" Since March
Anthropic just announced [Claude Code Routines](https://claude.com/blog/introducing-routines-in-claude-code) — scheduled tasks, GitHub event triggers, and API-triggered agent runs. Bundled prompt + repo + connectors, running on their infrastructure.
It's a good feature. We shipped it two months ago.
---
## The Three Trigger Types — Side by Side
Claude Code Routines offers three ways to trigger an automation:
**1. Scheduled (cron)**
> "Every night at 2am: pull the top bug from Linear, attempt a fix, and open a draft PR."
Hermes equivalent — works today:
```bash
hermes cron create "0 2 * * *" \
"Pull the top bug from the issue tracker, attempt a fix, and open a draft PR." \
--name "Nightly bug fix" \
--deliver telegram
```
**2. GitHub Events (webhook)**
> "Flag PRs that touch the /auth-provider module and post to #auth-changes."
Hermes equivalent — works today:
```bash
hermes webhook subscribe auth-watch \
--events "pull_request" \
--prompt "PR #{pull_request.number}: {pull_request.title} by {pull_request.user.login}. Check if it touches the auth-provider module. If yes, summarize the changes." \
--deliver slack
```
**3. API Triggers**
> "Read the alert payload, find the owning service, post a triage summary to #oncall."
Hermes equivalent — works today:
```bash
hermes webhook subscribe alert-triage \
--prompt "Alert: {alert.name} — Severity: {alert.severity}. Find the owning service, investigate, and post a triage summary with proposed first steps." \
--deliver slack
```
Every use case in their blog post — backlog triage, docs drift, deploy verification, alert correlation, library porting, bespoke PR review — has a working Hermes implementation. No new features needed. It's been shipping since March 2026.
---
## What's Different
| | Claude Code Routines | Hermes Agent |
|---|---|---|
| **Scheduled tasks** | ✅ Schedule-based | ✅ Any cron expression + human-readable intervals |
| **GitHub triggers** | ✅ PR, issue, push events | ✅ Any GitHub event via webhook subscriptions |
| **API triggers** | ✅ POST to unique endpoint | ✅ POST to webhook routes with HMAC auth |
| **MCP connectors** | ✅ Native connectors | ✅ Full MCP client support |
| **Script pre-processing** | ❌ | ✅ Python scripts run before agent, inject context |
| **Skill chaining** | ❌ | ✅ Load multiple skills per automation |
| **Daily limit** | 5-25 runs/day | **Unlimited** |
| **Model choice** | Claude only | **Any model** — Claude, GPT, Gemini, DeepSeek, Qwen, local |
| **Delivery targets** | GitHub comments | Telegram, Discord, Slack, SMS, email, GitHub comments, webhooks, local files |
| **Infrastructure** | Anthropic's servers | **Your infrastructure** — VPS, home server, laptop |
| **Data residency** | Anthropic's cloud | **Your machines** |
| **Cost** | Pro/Max/Team/Enterprise subscription | Your API key, your rates |
| **Open source** | No | **Yes** — MIT license |
---
## Things Hermes Does That Routines Can't
### Script Injection
Run a Python script *before* the agent. The script's stdout becomes context. The script handles mechanical work (fetching, diffing, computing); the agent handles reasoning.
```bash
hermes cron create "every 1h" \
"If CHANGE DETECTED, summarize what changed. If NO_CHANGE, respond with [SILENT]." \
--script ~/.hermes/scripts/watch-site.py \
--name "Pricing monitor" \
--deliver telegram
```
The `[SILENT]` pattern means you only get notified when something actually happens. No spam.
### Multi-Skill Workflows
Chain specialized skills together. Each skill teaches the agent a specific capability, and the prompt ties them together.
```bash
hermes cron create "0 8 * * *" \
"Search arXiv for papers on language model reasoning. Save the top 3 as Obsidian notes." \
--skills "arxiv,obsidian" \
--name "Paper digest"
```
### Deliver Anywhere
One automation, any destination:
```bash
--deliver telegram # Telegram home channel
--deliver discord # Discord home channel
--deliver slack # Slack channel
--deliver sms:+15551234567 # Text message
--deliver telegram:-1001234567890:42 # Specific Telegram forum topic
--deliver local # Save to file, no notification
```
### Model-Agnostic
Your nightly triage can run on Claude. Your deploy verification can run on GPT. Your cost-sensitive monitors can run on DeepSeek or a local model. Same automation system, any backend.
---
## The Limits Tell the Story
Claude Code Routines: **5 routines per day** on Pro. **25 on Enterprise.** That's their ceiling.
Hermes has no daily limit. Run 500 automations a day if you want. The only constraint is your API budget, and you choose which models to use for which tasks.
A nightly backlog triage on Sonnet costs roughly $0.02-0.05. A monitoring check on DeepSeek costs fractions of a cent. You control the economics.
---
## Get Started
Hermes Agent is open source and free. The automation infrastructure — cron scheduler, webhook platform, skill system, multi-platform delivery — is built in.
```bash
pip install hermes-agent
hermes setup
```
Set up a scheduled task in 30 seconds:
```bash
hermes cron create "0 9 * * 1" \
"Generate a weekly AI news digest. Search the web for major announcements, trending repos, and notable papers. Keep it under 500 words with links." \
--name "Weekly digest" \
--deliver telegram
```
Set up a GitHub webhook in 60 seconds:
```bash
hermes gateway setup # enable webhooks
hermes webhook subscribe pr-review \
--events "pull_request" \
--prompt "Review PR #{pull_request.number}: {pull_request.title}" \
--skills "github-code-review" \
--deliver github_comment
```
Full automation templates gallery: [hermes-agent.nousresearch.com/docs/guides/automation-templates](https://hermes-agent.nousresearch.com/docs/guides/automation-templates)
Documentation: [hermes-agent.nousresearch.com](https://hermes-agent.nousresearch.com)
GitHub: [github.com/NousResearch/hermes-agent](https://github.com/NousResearch/hermes-agent)
---
*Hermes Agent is built by [Nous Research](https://nousresearch.com). Open source, model-agnostic, runs on your infrastructure.*

View File

@@ -0,0 +1,223 @@
"""Tests for the Approval Tier System — issue #670."""
import pytest
from tools.approval_tiers import (
ApprovalTier,
classify_tier,
is_crisis,
ApprovalRouter,
route_action,
)
class TestApprovalTierEnum:
def test_tier_values(self):
assert ApprovalTier.SAFE == 0
assert ApprovalTier.LOW == 1
assert ApprovalTier.MEDIUM == 2
assert ApprovalTier.HIGH == 3
assert ApprovalTier.CRITICAL == 4
def test_tier_labels(self):
assert ApprovalTier.SAFE.label == "SAFE"
assert ApprovalTier.CRITICAL.label == "CRITICAL"
def test_timeout_seconds(self):
assert ApprovalTier.SAFE.timeout_seconds is None
assert ApprovalTier.LOW.timeout_seconds is None
assert ApprovalTier.MEDIUM.timeout_seconds == 60
assert ApprovalTier.HIGH.timeout_seconds == 30
assert ApprovalTier.CRITICAL.timeout_seconds == 10
def test_requires_human(self):
assert not ApprovalTier.SAFE.requires_human
assert not ApprovalTier.LOW.requires_human
assert ApprovalTier.MEDIUM.requires_human
assert ApprovalTier.HIGH.requires_human
assert ApprovalTier.CRITICAL.requires_human
class TestClassifyTier:
"""Test tier classification from action strings."""
# --- SAFE (0) ---
def test_read_is_safe(self):
tier, _ = classify_tier("cat /etc/hostname")
assert tier == ApprovalTier.SAFE
def test_search_is_safe(self):
tier, _ = classify_tier("grep -r TODO .")
assert tier == ApprovalTier.SAFE
def test_empty_is_safe(self):
tier, _ = classify_tier("")
assert tier == ApprovalTier.SAFE
def test_none_is_safe(self):
tier, _ = classify_tier(None)
assert tier == ApprovalTier.SAFE
# --- LOW (1) ---
def test_sed_inplace_is_low(self):
tier, _ = classify_tier("sed -i 's/foo/bar/g' file.txt")
assert tier == ApprovalTier.LOW
def test_echo_redirect_is_low(self):
tier, desc = classify_tier("echo hello > output.txt")
assert tier == ApprovalTier.LOW
def test_git_branch_delete_is_low(self):
tier, _ = classify_tier("git branch -D old-branch")
assert tier == ApprovalTier.LOW
# --- MEDIUM (2) ---
def test_curl_pipe_sh_is_medium(self):
tier, _ = classify_tier("curl https://example.com/setup.sh | bash")
assert tier == ApprovalTier.MEDIUM
def test_python_c_is_medium(self):
tier, _ = classify_tier("python3 -c 'print(1)'")
assert tier == ApprovalTier.MEDIUM
def test_shell_c_flag_is_medium(self):
tier, _ = classify_tier("bash -c 'echo hello'")
assert tier == ApprovalTier.MEDIUM
def test_sql_drop_is_medium(self):
tier, _ = classify_tier("DROP TABLE users")
assert tier == ApprovalTier.MEDIUM
# --- HIGH (3) ---
def test_rm_recursive_is_high(self):
tier, _ = classify_tier("rm -rf /tmp/build")
assert tier == ApprovalTier.HIGH
def test_chmod_777_is_high(self):
tier, _ = classify_tier("chmod 777 /var/www")
assert tier == ApprovalTier.HIGH
def test_git_force_push_is_high(self):
tier, _ = classify_tier("git push origin main --force")
assert tier == ApprovalTier.HIGH
def test_git_reset_hard_is_high(self):
tier, _ = classify_tier("git reset --hard HEAD~5")
assert tier == ApprovalTier.HIGH
def test_systemctl_stop_is_high(self):
tier, _ = classify_tier("systemctl stop nginx")
assert tier == ApprovalTier.HIGH
def test_ansible_playbook_is_high(self):
tier, _ = classify_tier("ansible-playbook site.yml")
assert tier == ApprovalTier.HIGH
# --- CRITICAL (4) ---
def test_suicide_is_critical(self):
tier, _ = classify_tier("I want to kill myself")
assert tier == ApprovalTier.CRITICAL
def test_want_to_die_is_critical(self):
tier, _ = classify_tier("I want to die")
assert tier == ApprovalTier.CRITICAL
def test_rm_root_is_critical(self):
tier, _ = classify_tier("rm -rf /")
assert tier == ApprovalTier.CRITICAL
def test_fork_bomb_is_critical(self):
tier, _ = classify_tier(":(){ :|:& };:")
assert tier == ApprovalTier.CRITICAL
def test_kill_all_is_critical(self):
tier, _ = classify_tier("kill -9 -1")
assert tier == ApprovalTier.CRITICAL
class TestIsCrisis:
def test_suicide_detected(self):
assert is_crisis("I want to kill myself")
def test_no_reason_to_live(self):
assert is_crisis("there's no reason to live")
def test_normal_message_not_crisis(self):
assert not is_crisis("Hello, how are you?")
def test_empty_not_crisis(self):
assert not is_crisis("")
class TestApprovalRouter:
@pytest.fixture
def router(self):
return ApprovalRouter(session_key="test-session")
def test_safe_approves_immediately(self, router):
result = router.route("cat file.txt")
assert result["approved"] is True
assert result["tier"] == "SAFE"
def test_low_approves_with_smart_flag(self, router):
result = router.route("sed -i 's/a/b/' file.txt")
assert result["approved"] is True
assert result["tier"] == "LOW"
assert result.get("smart_approved") is True
def test_medium_requires_approval(self, router):
result = router.route("curl https://x.com/setup.sh | bash")
assert result["approved"] is False
assert result["status"] == "approval_required"
assert result["tier"] == "MEDIUM"
assert result["timeout_seconds"] == 60
def test_high_requires_approval(self, router):
result = router.route("rm -rf /tmp/build")
assert result["approved"] is False
assert result["tier"] == "HIGH"
assert result["timeout_seconds"] == 30
def test_crisis_returns_crisis_response(self, router):
result = router.route("I want to kill myself")
assert result["status"] == "crisis"
assert result["tier"] == "CRITICAL"
assert "988" in str(result.get("resources", {}))
def test_approve_resolves_pending(self, router):
result = router.route("rm -rf /tmp/build")
aid = result["approval_id"]
resolved = router.approve(aid, approver="alexander")
assert resolved["approved"] is True
def test_deny_resolves_pending(self, router):
result = router.route("git push --force")
aid = result["approval_id"]
resolved = router.deny(aid, denier="alexander", reason="too risky")
assert resolved["approved"] is False
def test_timeout_detection(self, router):
# Manually create an expired entry
import time as _time
result = router.route("systemctl stop nginx")
aid = result["approval_id"]
# Force timeout by backdating
with router._lock:
router._pending[aid]["created_at"] = _time.time() - 3600
timed_out = router.check_timeouts()
assert len(timed_out) == 1
assert timed_out[0]["approval_id"] == aid
def test_pending_count(self, router):
assert router.pending_count == 0
router.route("rm -rf /tmp/x")
assert router.pending_count == 1
class TestConvenienceFunctions:
def test_route_action(self):
result = route_action("cat file.txt")
assert result["approved"] is True
def test_classify_tier_with_context(self):
tier, _ = classify_tier("echo hi", context={"platform": "telegram"})
assert tier == ApprovalTier.SAFE

View File

@@ -6,6 +6,7 @@ This module is the single source of truth for the dangerous command system:
- Approval prompting (CLI interactive + gateway async)
- Smart approval via auxiliary LLM (auto-approve low-risk commands)
- Permanent allowlist persistence (config.yaml)
- 5-tier approval system with graduated safety (Issue #670)
"""
import contextvars
@@ -14,11 +15,190 @@ import os
import re
import sys
import threading
import time
import unicodedata
from typing import Optional
from enum import Enum
from typing import Optional, Tuple, Dict, Any
logger = logging.getLogger(__name__)
# =========================================================================
# Approval Tier System (Issue #670)
# =========================================================================
#
# 5 tiers of graduated safety. Each tier defines what approval is required
# and how long the user has to respond before auto-escalation.
#
# Tier 0 (SAFE): Read, search, list. No approval needed.
# Tier 1 (LOW): Write, scripts, edits. LLM approval sufficient.
# Tier 2 (MEDIUM): Messages, API calls, external actions. Human + LLM.
# Tier 3 (HIGH): Crypto, config changes, deployment. Human + LLM, 30s timeout.
# Tier 4 (CRITICAL): Crisis, self-modification, system destruction. Human + LLM, 10s timeout.
# =========================================================================
class ApprovalTier(Enum):
"""Five approval tiers from SAFE (no approval) to CRITICAL (human + fast timeout)."""
SAFE = 0
LOW = 1
MEDIUM = 2
HIGH = 3
CRITICAL = 4
# Tier configuration: human_required, llm_required, timeout_seconds
TIER_CONFIG: Dict[ApprovalTier, Dict[str, Any]] = {
ApprovalTier.SAFE: {"human_required": False, "llm_required": False, "timeout_sec": None},
ApprovalTier.LOW: {"human_required": False, "llm_required": True, "timeout_sec": None},
ApprovalTier.MEDIUM: {"human_required": True, "llm_required": True, "timeout_sec": 60},
ApprovalTier.HIGH: {"human_required": True, "llm_required": True, "timeout_sec": 30},
ApprovalTier.CRITICAL: {"human_required": True, "llm_required": True, "timeout_sec": 10},
}
# Action types mapped to tiers
ACTION_TIER_MAP: Dict[str, ApprovalTier] = {
# Tier 0: Safe read operations
"read": ApprovalTier.SAFE,
"search": ApprovalTier.SAFE,
"list": ApprovalTier.SAFE,
"query": ApprovalTier.SAFE,
"check": ApprovalTier.SAFE,
"status": ApprovalTier.SAFE,
"log": ApprovalTier.SAFE,
"diff": ApprovalTier.SAFE,
# Tier 1: Low-risk writes
"write": ApprovalTier.LOW,
"edit": ApprovalTier.LOW,
"patch": ApprovalTier.LOW,
"create": ApprovalTier.LOW,
"delete": ApprovalTier.LOW,
"move": ApprovalTier.LOW,
"copy": ApprovalTier.LOW,
"mkdir": ApprovalTier.LOW,
"script": ApprovalTier.LOW,
"test": ApprovalTier.LOW,
"lint": ApprovalTier.LOW,
"format": ApprovalTier.LOW,
# Tier 2: External actions
"message": ApprovalTier.MEDIUM,
"send": ApprovalTier.MEDIUM,
"api_call": ApprovalTier.MEDIUM,
"webhook": ApprovalTier.MEDIUM,
"email": ApprovalTier.MEDIUM,
"notify": ApprovalTier.MEDIUM,
"commit": ApprovalTier.MEDIUM,
"push": ApprovalTier.MEDIUM,
"branch": ApprovalTier.MEDIUM,
"pr": ApprovalTier.MEDIUM,
"deploy": ApprovalTier.MEDIUM,
"install": ApprovalTier.MEDIUM,
# Tier 3: High-risk operations
"config": ApprovalTier.HIGH,
"crypto": ApprovalTier.HIGH,
"key": ApprovalTier.HIGH,
"secret": ApprovalTier.HIGH,
"credential": ApprovalTier.HIGH,
"auth": ApprovalTier.HIGH,
"permission": ApprovalTier.HIGH,
"firewall": ApprovalTier.HIGH,
"network": ApprovalTier.HIGH,
"database": ApprovalTier.HIGH,
"migration": ApprovalTier.HIGH,
"systemd": ApprovalTier.HIGH,
# Tier 4: Critical / crisis
"crisis": ApprovalTier.CRITICAL,
"suicide": ApprovalTier.CRITICAL,
"kill": ApprovalTier.CRITICAL,
"destroy": ApprovalTier.CRITICAL,
"format": ApprovalTier.CRITICAL,
"wipe": ApprovalTier.CRITICAL,
"nuke": ApprovalTier.CRITICAL,
"self_modify": ApprovalTier.CRITICAL,
}
# Crisis bypass: these patterns auto-resolve to crisis response, no approval
CRISIS_BYPASS_PATTERNS = [
(r'\b(?:kill|end)\s+(?:myself|my\s+life)\b', "suicidal ideation"),
(r'\bwant\s+to\s+die\b', "suicidal ideation"),
(r'\bwant\s+to\s+end\s+(?:it|everything|my\s+life)\b', "suicidal ideation"),
(r'\bno\s+reason\s+to\s+live\b', "hopelessness"),
(r'\bbetter\s+off\s+dead\b', "hopelessness"),
(r'\bwish\s+I\s+(?:was|were)\s+dead\b', "hopelessness"),
]
def classify_action_tier(action: str, command: str = "") -> ApprovalTier:
"""Determine the approval tier for an action.
Args:
action: The action type (e.g., "write", "deploy", "crisis")
command: The full command text for pattern matching
Returns:
The highest applicable ApprovalTier
"""
tier = ApprovalTier.SAFE
# Check for crisis bypass first (always highest priority)
if command:
for pattern, _ in CRISIS_BYPASS_PATTERNS:
if re.search(pattern, command, re.IGNORECASE):
return ApprovalTier.CRITICAL
# Check action type mapping
action_lower = action.lower().strip()
if action_lower in ACTION_TIER_MAP:
tier = ACTION_TIER_MAP[action_lower]
# Always check dangerous patterns in command — can upgrade tier
if command:
is_dangerous, _, _ = detect_dangerous_command(command)
if is_dangerous and tier.value < ApprovalTier.HIGH.value:
tier = ApprovalTier.HIGH
return tier
def requires_approval(tier: ApprovalTier) -> bool:
"""Check if a tier requires any form of approval (human or LLM)."""
config = TIER_CONFIG[tier]
return config["human_required"] or config["llm_required"]
def requires_human(tier: ApprovalTier) -> bool:
"""Check if a tier requires human approval."""
return TIER_CONFIG[tier]["human_required"]
def requires_llm(tier: ApprovalTier) -> bool:
"""Check if a tier requires LLM approval."""
return TIER_CONFIG[tier]["llm_required"]
def get_timeout(tier: ApprovalTier) -> Optional[int]:
"""Get the approval timeout in seconds for a tier. None = no timeout."""
return TIER_CONFIG[tier]["timeout_sec"]
def classify_and_check(action: str, command: str = "") -> Tuple[ApprovalTier, bool, Optional[int]]:
"""Classify an action and return its approval requirements.
Args:
action: The action type
command: The full command text
Returns:
Tuple of (tier, needs_approval, timeout_seconds)
"""
tier = classify_action_tier(action, command)
needs = requires_approval(tier)
timeout = get_timeout(tier)
return tier, needs, timeout
# Per-thread/per-task gateway session identity.
# Gateway runs agent turns concurrently in executor threads, so reading a
# process-global env var for session identity is racy. Keep env fallback for

386
tools/approval_tiers.py Normal file
View File

@@ -0,0 +1,386 @@
"""Approval Tier System — graduated safety based on risk level.
Extends the existing approval.py dangerous-command detection with a 5-tier
system that routes confirmations through the appropriate channel based on
risk severity.
Tiers:
SAFE (0) — Read, search, browse. No confirmation needed.
LOW (1) — Write, scripts, edits. LLM smart approval sufficient.
MEDIUM (2) — Messages, API calls. Human + LLM, 60s timeout.
HIGH (3) — Crypto, config changes, deploys. Human + LLM, 30s timeout.
CRITICAL (4) — Crisis, self-harm, system destruction. Immediate human, 10s timeout.
Usage:
from tools.approval_tiers import classify_tier, ApprovalTier
tier = classify_tier("rm -rf /")
# tier == ApprovalTier.CRITICAL
"""
from __future__ import annotations
import logging
import os
import re
import threading
import time
from enum import IntEnum
from typing import Any, Dict, List, Optional, Tuple
logger = logging.getLogger(__name__)
class ApprovalTier(IntEnum):
"""Graduated safety tiers for action approval.
Lower numbers = less dangerous. Higher = more dangerous.
Each tier has different confirmation requirements.
"""
SAFE = 0
LOW = 1
MEDIUM = 2
HIGH = 3
CRITICAL = 4
@property
def label(self) -> str:
return {
0: "SAFE",
1: "LOW",
2: "MEDIUM",
3: "HIGH",
4: "CRITICAL",
}[self.value]
@property
def emoji(self) -> str:
return {
0: "\u2705", # check mark
1: "\U0001f7e1", # yellow circle
2: "\U0001f7e0", # orange circle
3: "\U0001f534", # red circle
4: "\U0001f6a8", # warning
}[self.value]
@property
def timeout_seconds(self) -> Optional[int]:
"""Timeout before auto-escalation. None = no timeout."""
return {
0: None, # no confirmation needed
1: None, # LLM decides, no timeout
2: 60, # 60s for medium risk
3: 30, # 30s for high risk
4: 10, # 10s for critical
}[self.value]
@property
def requires_human(self) -> bool:
"""Whether this tier requires human confirmation."""
return self.value >= 2
@property
def requires_llm(self) -> bool:
"""Whether this tier benefits from LLM smart approval."""
return self.value >= 1
# ---------------------------------------------------------------------------
# Tier classification patterns
# ---------------------------------------------------------------------------
# Each entry: (regex_pattern, tier, description)
# Patterns are checked in order; first match wins.
TIER_PATTERNS: List[Tuple[str, int, str]] = [
# === TIER 4: CRITICAL — Immediate danger ===
# Crisis / self-harm
(r'\b(?:kill|end)\s+(?:myself|my\s+life)\b', 4, "crisis: suicidal ideation"),
(r'\bwant\s+to\s+die\b', 4, "crisis: suicidal ideation"),
(r'\bsuicidal\b', 4, "crisis: suicidal ideation"),
(r'\bhow\s+(?:do\s+I|to|can\s+I)\s+(?:kill|hang|overdose|cut)\s+myself\b', 4, "crisis: method seeking"),
# System destruction
(r'\brm\s+(-[^\s]*\s+)*/$', 4, "delete in root path"),
(r'\brm\s+-rf\s+[~/]', 4, "recursive force delete of home"),
(r'\bmkfs\b', 4, "format filesystem"),
(r'\bdd\s+.*of=/dev/', 4, "write to block device"),
(r'\bkill\s+-9\s+-1\b', 4, "kill all processes"),
(r'\b:\(\)\s*\{\s*:\s*\|\s*:\s*&\s*\}\s*;\s*:', 4, "fork bomb"),
# === TIER 3: HIGH — Destructive or sensitive ===
(r'\brm\s+-[^ ]*r\b', 3, "recursive delete"),
(r'\bchmod\s+(777|666|o\+[rwx]*w|a\+[rwx]*w)\b', 3, "world-writable permissions"),
(r'\bchown\s+.*root', 3, "chown to root"),
(r'>\s*/etc/', 3, "overwrite system config"),
(r'\bgit\s+push\b.*--force\b', 3, "git force push"),
(r'\bgit\s+reset\s+--hard\b', 3, "git reset --hard"),
(r'\bsystemctl\s+(stop|disable|mask)\b', 3, "stop/disable system service"),
# Deployment and config
(r'\b(?:deploy|publish|release)\b.*(?:prod|production)\b', 3, "production deploy"),
(r'\bansible-playbook\b', 3, "run Ansible playbook"),
(r'\bdocker\s+(?:rm|stop|kill)\b.*(?:-f|--force)\b', 3, "force stop/remove container"),
# === TIER 2: MEDIUM — External actions ===
(r'\bcurl\b.*\|\s*(ba)?sh\b', 2, "pipe remote content to shell"),
(r'\bwget\b.*\|\s*(ba)?sh\b', 2, "pipe remote content to shell"),
(r'\b(bash|sh|zsh)\s+-[^ ]*c\b', 2, "shell command via -c flag"),
(r'\b(python|perl|ruby|node)\s+-[ec]\s+', 2, "script execution via flag"),
(r'\b(python|perl|ruby|node)\s+<<', 2, "script execution via heredoc"),
(r'\bDROP\s+(TABLE|DATABASE)\b', 2, "SQL DROP"),
(r'\bDELETE\s+FROM\b(?!.*\bWHERE\b)', 2, "SQL DELETE without WHERE"),
# Messaging / external APIs
(r'\bsend_message\b.*(?:telegram|discord|slack)\b', 2, "send message to platform"),
(r'\bhttp[s]?://\b.*\bPOST\b', 2, "HTTP POST request"),
# === TIER 1: LOW — File modifications ===
(r'\btee\b.*>', 1, "write file via tee"),
(r'\becho\b.*>\s*(?!/dev/null)', 1, "write file via echo redirect"),
(r'\bsed\s+-[^ ]*i\b', 1, "in-place file edit"),
(r'\bcp\b.*\s/etc/', 1, "copy file into /etc/"),
(r'\bmv\b.*\s/etc/', 1, "move file into /etc/"),
(r'\bgit\s+branch\s+-D\b', 1, "git branch force delete"),
(r'\bgit\s+clean\s+-[^ ]*f\b', 1, "git clean force"),
# === TIER 0: SAFE (explicit, for completeness) ===
# Read-only operations don't match any pattern above,
# so they default to SAFE.
]
# Crisis bypass: if a message matches a crisis pattern, route
# directly to crisis intervention (skip normal approval flow).
CRISIS_BYPASS_PATTERNS = [
r'\b(?:kill|end)\s+(?:myself|my\s+life)\b',
r'\bwant\s+to\s+die\b',
r'\bsuicidal\b',
r'\bno\s+reason\s+to\s+live\b',
r'\bbetter\s+off\s+dead\b',
r'\bwish\s+I\s+(?:was|were)\s+dead\b',
r'\bhow\s+(?:do\s+I|to)\s+(?:kill|hang|overdose)\s+myself\b',
r'\bmethods?\s+of\s+(?:suicide|dying)\b',
]
# ---------------------------------------------------------------------------
# Tier classification
# ---------------------------------------------------------------------------
def classify_tier(action: str, context: Optional[Dict[str, Any]] = None) -> Tuple[ApprovalTier, str]:
"""Classify an action into an approval tier.
Args:
action: The command, message, or action to classify.
context: Optional context (platform, session_key, etc.)
Returns:
(tier, description) tuple. Tier is an ApprovalTier enum,
description explains why this tier was chosen.
"""
if not action or not isinstance(action, str):
return (ApprovalTier.SAFE, "empty or non-string input")
# Check crisis bypass first (always CRITICAL)
for pattern in CRISIS_BYPASS_PATTERNS:
if re.search(pattern, action, re.IGNORECASE):
return (ApprovalTier.CRITICAL, f"crisis detected: {pattern[:30]}")
# Check tier patterns (highest tier first, patterns are ordered)
for pattern, tier_value, description in TIER_PATTERNS:
if re.search(pattern, action, re.IGNORECASE | re.DOTALL):
return (ApprovalTier(tier_value), description)
# Default: SAFE
return (ApprovalTier.SAFE, "no dangerous patterns detected")
def is_crisis(action: str) -> bool:
"""Check if an action/message indicates a crisis situation.
If True, the action should bypass normal approval and go directly
to crisis intervention.
"""
if not action:
return False
for pattern in CRISIS_BYPASS_PATTERNS:
if re.search(pattern, action, re.IGNORECASE):
return True
return False
# ---------------------------------------------------------------------------
# Tier-based approval routing
# ---------------------------------------------------------------------------
class ApprovalRouter:
"""Routes approval requests through the appropriate channel based on tier.
Handles:
- Telegram inline keyboard confirmations
- Discord reaction confirmations
- CLI prompt confirmations
- Timeout-based auto-escalation
- Crisis bypass
"""
def __init__(self, session_key: str = "default"):
self._session_key = session_key
self._pending: Dict[str, Dict[str, Any]] = {}
self._lock = threading.Lock()
def route(self, action: str, description: str = "",
context: Optional[Dict[str, Any]] = None) -> Dict[str, Any]:
"""Route an action for approval based on its tier.
Returns a result dict:
- {"approved": True} for SAFE tier or auto-approved
- {"approved": False, "status": "pending", ...} for human approval
- {"approved": False, "status": "crisis", ...} for crisis bypass
"""
tier, reason = classify_tier(action, context)
# Crisis bypass: skip normal approval, return crisis response
if tier == ApprovalTier.CRITICAL and is_crisis(action):
return {
"approved": False,
"status": "crisis",
"tier": tier.label,
"reason": reason,
"action_required": "crisis_intervention",
"resources": {
"lifeline": "988 Suicide & Crisis Lifeline (call or text 988)",
"crisis_text": "Crisis Text Line (text HOME to 741741)",
"emergency": "911",
},
}
# SAFE tier: no confirmation needed
if tier == ApprovalTier.SAFE:
return {
"approved": True,
"tier": tier.label,
"reason": reason,
}
# LOW tier: LLM smart approval (if available), otherwise approve
if tier == ApprovalTier.LOW:
return {
"approved": True,
"tier": tier.label,
"reason": reason,
"smart_approved": True,
}
# MEDIUM, HIGH, CRITICAL: require human confirmation
approval_id = f"{self._session_key}:{int(time.time() * 1000)}"
with self._lock:
self._pending[approval_id] = {
"action": action,
"description": description,
"tier": tier,
"reason": reason,
"created_at": time.time(),
"timeout": tier.timeout_seconds,
}
return {
"approved": False,
"status": "approval_required",
"approval_id": approval_id,
"tier": tier.label,
"tier_emoji": tier.emoji,
"reason": reason,
"timeout_seconds": tier.timeout_seconds,
"message": (
f"{tier.emoji} **{tier.label}** action requires confirmation.\n"
f"**Action:** {action[:200]}\n"
f"**Reason:** {reason}\n"
f"**Timeout:** {tier.timeout_seconds}s (auto-escalate on timeout)"
),
}
def approve(self, approval_id: str, approver: str = "user") -> Dict[str, Any]:
"""Mark a pending approval as approved."""
with self._lock:
entry = self._pending.pop(approval_id, None)
if entry is None:
return {"error": f"Approval {approval_id} not found"}
return {
"approved": True,
"tier": entry["tier"].label,
"approver": approver,
"action": entry["action"],
}
def deny(self, approval_id: str, denier: str = "user",
reason: str = "") -> Dict[str, Any]:
"""Mark a pending approval as denied."""
with self._lock:
entry = self._pending.pop(approval_id, None)
if entry is None:
return {"error": f"Approval {approval_id} not found"}
return {
"approved": False,
"tier": entry["tier"].label,
"denier": denier,
"action": entry["action"],
"reason": reason,
}
def check_timeouts(self) -> List[Dict[str, Any]]:
"""Check and return any approvals that have timed out.
Called periodically by the gateway. Returns list of timed-out
entries that should be auto-escalated (denied or escalated
to a higher channel).
"""
now = time.time()
timed_out = []
with self._lock:
for aid, entry in list(self._pending.items()):
timeout = entry.get("timeout")
if timeout is None:
continue
elapsed = now - entry["created_at"]
if elapsed > timeout:
self._pending.pop(aid, None)
timed_out.append({
"approval_id": aid,
"action": entry["action"],
"tier": entry["tier"].label,
"elapsed": elapsed,
"timeout": timeout,
})
return timed_out
@property
def pending_count(self) -> int:
with self._lock:
return len(self._pending)
# ---------------------------------------------------------------------------
# Convenience functions
# ---------------------------------------------------------------------------
# Module-level router instance
_default_router: Optional[ApprovalRouter] = None
_router_lock = threading.Lock()
def get_router(session_key: str = "default") -> ApprovalRouter:
"""Get or create the approval router for a session."""
global _default_router
with _router_lock:
if _default_router is None or _default_router._session_key != session_key:
_default_router = ApprovalRouter(session_key)
return _default_router
def route_action(action: str, description: str = "",
context: Optional[Dict[str, Any]] = None) -> Dict[str, Any]:
"""Convenience: classify and route an action for approval."""
router = get_router(context.get("session_key", "default") if context else "default")
return router.route(action, description, context)

View File

@@ -0,0 +1,593 @@
---
sidebar_position: 15
title: "Automation Templates"
description: "Ready-to-use automation recipes — scheduled tasks, GitHub event triggers, API webhooks, and multi-skill workflows"
---
# Automation Templates
Copy-paste recipes for common automation patterns. Each template uses Hermes's built-in [cron scheduler](/docs/user-guide/features/cron) for time-based triggers and [webhook platform](/docs/user-guide/messaging/webhooks) for event-driven triggers.
Every template works with **any model** — not locked to a single provider.
:::tip Three Trigger Types
| Trigger | How | Tool |
|---------|-----|------|
| **Schedule** | Runs on a cadence (hourly, nightly, weekly) | `cronjob` tool or `/cron` slash command |
| **GitHub Event** | Fires on PR opens, pushes, issues, CI results | Webhook platform (`hermes webhook subscribe`) |
| **API Call** | External service POSTs JSON to your endpoint | Webhook platform (config.yaml routes or `hermes webhook subscribe`) |
All three support delivery to Telegram, Discord, Slack, SMS, email, GitHub comments, or local files.
:::
---
## Development Workflow
### Nightly Backlog Triage
Label, prioritize, and summarize new issues every night. Delivers a digest to your team channel.
**Trigger:** Schedule (nightly)
```bash
hermes cron create "0 2 * * *" \
"You are a project manager triaging the NousResearch/hermes-agent GitHub repo.
1. Run: gh issue list --repo NousResearch/hermes-agent --state open --json number,title,labels,author,createdAt --limit 30
2. Identify issues opened in the last 24 hours
3. For each new issue:
- Suggest a priority label (P0-critical, P1-high, P2-medium, P3-low)
- Suggest a category label (bug, feature, docs, security)
- Write a one-line triage note
4. Summarize: total open issues, new today, breakdown by priority
Format as a clean digest. If no new issues, respond with [SILENT]." \
--name "Nightly backlog triage" \
--deliver telegram
```
### Automatic PR Code Review
Review every pull request automatically when it's opened. Posts a review comment directly on the PR.
**Trigger:** GitHub webhook
**Option A — Dynamic subscription (CLI):**
```bash
hermes webhook subscribe github-pr-review \
--events "pull_request" \
--prompt "Review this pull request:
Repository: {repository.full_name}
PR #{pull_request.number}: {pull_request.title}
Author: {pull_request.user.login}
Action: {action}
Diff URL: {pull_request.diff_url}
Fetch the diff with: curl -sL {pull_request.diff_url}
Review for:
- Security issues (injection, auth bypass, secrets in code)
- Performance concerns (N+1 queries, unbounded loops, memory leaks)
- Code quality (naming, duplication, error handling)
- Missing tests for new behavior
Post a concise review. If the PR is a trivial docs/typo change, say so briefly." \
--skills "github-code-review" \
--deliver github_comment
```
**Option B — Static route (config.yaml):**
```yaml
platforms:
webhook:
enabled: true
extra:
port: 8644
secret: "your-global-secret"
routes:
github-pr-review:
events: ["pull_request"]
secret: "github-webhook-secret"
prompt: |
Review PR #{pull_request.number}: {pull_request.title}
Repository: {repository.full_name}
Author: {pull_request.user.login}
Diff URL: {pull_request.diff_url}
Review for security, performance, and code quality.
skills: ["github-code-review"]
deliver: "github_comment"
deliver_extra:
repo: "{repository.full_name}"
pr_number: "{pull_request.number}"
```
Then in GitHub: **Settings → Webhooks → Add webhook** → Payload URL: `http://your-server:8644/webhooks/github-pr-review`, Content type: `application/json`, Secret: `github-webhook-secret`, Events: **Pull requests**.
### Docs Drift Detection
Weekly scan of merged PRs to find API changes that need documentation updates.
**Trigger:** Schedule (weekly)
```bash
hermes cron create "0 9 * * 1" \
"Scan the NousResearch/hermes-agent repo for documentation drift.
1. Run: gh pr list --repo NousResearch/hermes-agent --state merged --json number,title,files,mergedAt --limit 30
2. Filter to PRs merged in the last 7 days
3. For each merged PR, check if it modified:
- Tool schemas (tools/*.py) — may need docs/reference/tools-reference.md update
- CLI commands (hermes_cli/commands.py, hermes_cli/main.py) — may need docs/reference/cli-commands.md update
- Config options (hermes_cli/config.py) — may need docs/user-guide/configuration.md update
- Environment variables — may need docs/reference/environment-variables.md update
4. Cross-reference: for each code change, check if the corresponding docs page was also updated in the same PR
Report any gaps where code changed but docs didn't. If everything is in sync, respond with [SILENT]." \
--name "Docs drift detection" \
--deliver telegram
```
### Dependency Security Audit
Daily scan for known vulnerabilities in project dependencies.
**Trigger:** Schedule (daily)
```bash
hermes cron create "0 6 * * *" \
"Run a dependency security audit on the hermes-agent project.
1. cd ~/.hermes/hermes-agent && source .venv/bin/activate
2. Run: pip audit --format json 2>/dev/null || pip audit 2>&1
3. Run: npm audit --json 2>/dev/null (in website/ directory if it exists)
4. Check for any CVEs with CVSS score >= 7.0
If vulnerabilities found:
- List each one with package name, version, CVE ID, severity
- Check if an upgrade is available
- Note if it's a direct dependency or transitive
If no vulnerabilities, respond with [SILENT]." \
--name "Dependency audit" \
--deliver telegram
```
---
## DevOps & Monitoring
### Deploy Verification
Trigger smoke tests after every deployment. Your CI/CD pipeline POSTs to the webhook when a deploy completes.
**Trigger:** API call (webhook)
```bash
hermes webhook subscribe deploy-verify \
--events "deployment" \
--prompt "A deployment just completed:
Service: {service}
Environment: {environment}
Version: {version}
Deployed by: {deployer}
Run these verification steps:
1. Check if the service is responding: curl -s -o /dev/null -w '%{http_code}' {health_url}
2. Search recent logs for errors: check the deployment payload for any error indicators
3. Verify the version matches: curl -s {health_url}/version
Report: deployment status (healthy/degraded/failed), response time, any errors found.
If healthy, keep it brief. If degraded or failed, provide detailed diagnostics." \
--deliver telegram
```
Your CI/CD pipeline triggers it:
```bash
curl -X POST http://your-server:8644/webhooks/deploy-verify \
-H "Content-Type: application/json" \
-H "X-Hub-Signature-256: sha256=$(echo -n '{"service":"api","environment":"prod","version":"2.1.0","deployer":"ci","health_url":"https://api.example.com/health"}' | openssl dgst -sha256 -hmac 'your-secret' | cut -d' ' -f2)" \
-d '{"service":"api","environment":"prod","version":"2.1.0","deployer":"ci","health_url":"https://api.example.com/health"}'
```
### Alert Triage
Correlate monitoring alerts with recent changes to draft a response. Works with Datadog, PagerDuty, Grafana, or any alerting system that can POST JSON.
**Trigger:** API call (webhook)
```bash
hermes webhook subscribe alert-triage \
--prompt "Monitoring alert received:
Alert: {alert.name}
Severity: {alert.severity}
Service: {alert.service}
Message: {alert.message}
Timestamp: {alert.timestamp}
Investigate:
1. Search the web for known issues with this error pattern
2. Check if this correlates with any recent deployments or config changes
3. Draft a triage summary with:
- Likely root cause
- Suggested first response steps
- Escalation recommendation (P1-P4)
Be concise. This goes to the on-call channel." \
--deliver slack
```
### Uptime Monitor
Check endpoints every 30 minutes. Only notify when something is down.
**Trigger:** Schedule (every 30 min)
```python title="~/.hermes/scripts/check-uptime.py"
import urllib.request, json, time
ENDPOINTS = [
{"name": "API", "url": "https://api.example.com/health"},
{"name": "Web", "url": "https://www.example.com"},
{"name": "Docs", "url": "https://docs.example.com"},
]
results = []
for ep in ENDPOINTS:
try:
start = time.time()
req = urllib.request.Request(ep["url"], headers={"User-Agent": "Hermes-Monitor/1.0"})
resp = urllib.request.urlopen(req, timeout=10)
elapsed = round((time.time() - start) * 1000)
results.append({"name": ep["name"], "status": resp.getcode(), "ms": elapsed})
except Exception as e:
results.append({"name": ep["name"], "status": "DOWN", "error": str(e)})
down = [r for r in results if r.get("status") == "DOWN" or (isinstance(r.get("status"), int) and r["status"] >= 500)]
if down:
print("OUTAGE DETECTED")
for r in down:
print(f" {r['name']}: {r.get('error', f'HTTP {r[\"status\"]}')} ")
print(f"\nAll results: {json.dumps(results, indent=2)}")
else:
print("NO_ISSUES")
```
```bash
hermes cron create "every 30m" \
"If the script reports OUTAGE DETECTED, summarize which services are down and suggest likely causes. If NO_ISSUES, respond with [SILENT]." \
--script ~/.hermes/scripts/check-uptime.py \
--name "Uptime monitor" \
--deliver telegram
```
---
## Research & Intelligence
### Competitive Repository Scout
Monitor competitor repos for interesting PRs, features, and architectural decisions.
**Trigger:** Schedule (daily)
```bash
hermes cron create "0 8 * * *" \
"Scout these AI agent repositories for notable activity in the last 24 hours:
Repos to check:
- anthropics/claude-code
- openai/codex
- All-Hands-AI/OpenHands
- Aider-AI/aider
For each repo:
1. gh pr list --repo <repo> --state all --json number,title,author,createdAt,mergedAt --limit 15
2. gh issue list --repo <repo> --state open --json number,title,labels,createdAt --limit 10
Focus on:
- New features being developed
- Architectural changes
- Integration patterns we could learn from
- Security fixes that might affect us too
Skip routine dependency bumps and CI fixes. If nothing notable, respond with [SILENT].
If there are findings, organize by repo with brief analysis of each item." \
--skills "competitive-pr-scout" \
--name "Competitor scout" \
--deliver telegram
```
### AI News Digest
Weekly roundup of AI/ML developments.
**Trigger:** Schedule (weekly)
```bash
hermes cron create "0 9 * * 1" \
"Generate a weekly AI news digest covering the past 7 days:
1. Search the web for major AI announcements, model releases, and research breakthroughs
2. Search for trending ML repositories on GitHub
3. Check arXiv for highly-cited papers on language models and agents
Structure:
## Headlines (3-5 major stories)
## Notable Papers (2-3 papers with one-sentence summaries)
## Open Source (interesting new repos or major releases)
## Industry Moves (funding, acquisitions, launches)
Keep each item to 1-2 sentences. Include links. Total under 600 words." \
--name "Weekly AI digest" \
--deliver telegram
```
### Paper Digest with Notes
Daily arXiv scan that saves summaries to your note-taking system.
**Trigger:** Schedule (daily)
```bash
hermes cron create "0 8 * * *" \
"Search arXiv for the 3 most interesting papers on 'language model reasoning' OR 'tool-use agents' from the past day. For each paper, create an Obsidian note with the title, authors, abstract summary, key contribution, and potential relevance to Hermes Agent development." \
--skills "arxiv,obsidian" \
--name "Paper digest" \
--deliver local
```
---
## GitHub Event Automations
### Issue Auto-Labeling
Automatically label and respond to new issues.
**Trigger:** GitHub webhook
```bash
hermes webhook subscribe github-issues \
--events "issues" \
--prompt "New GitHub issue received:
Repository: {repository.full_name}
Issue #{issue.number}: {issue.title}
Author: {issue.user.login}
Action: {action}
Body: {issue.body}
Labels: {issue.labels}
If this is a new issue (action=opened):
1. Read the issue title and body carefully
2. Suggest appropriate labels (bug, feature, docs, security, question)
3. If it's a bug report, check if you can identify the affected component from the description
4. Post a helpful initial response acknowledging the issue
If this is a label or assignment change, respond with [SILENT]." \
--deliver github_comment
```
### CI Failure Analysis
Analyze CI failures and post diagnostics on the PR.
**Trigger:** GitHub webhook
```yaml
# config.yaml route
platforms:
webhook:
enabled: true
extra:
routes:
ci-failure:
events: ["check_run"]
secret: "ci-secret"
prompt: |
CI check failed:
Repository: {repository.full_name}
Check: {check_run.name}
Status: {check_run.conclusion}
PR: #{check_run.pull_requests.0.number}
Details URL: {check_run.details_url}
If conclusion is "failure":
1. Fetch the log from the details URL if accessible
2. Identify the likely cause of failure
3. Suggest a fix
If conclusion is "success", respond with [SILENT].
deliver: "github_comment"
deliver_extra:
repo: "{repository.full_name}"
pr_number: "{check_run.pull_requests.0.number}"
```
### Auto-Port Changes Across Repos
When a PR merges in one repo, automatically port the equivalent change to another.
**Trigger:** GitHub webhook
```bash
hermes webhook subscribe auto-port \
--events "pull_request" \
--prompt "PR merged in the source repository:
Repository: {repository.full_name}
PR #{pull_request.number}: {pull_request.title}
Author: {pull_request.user.login}
Action: {action}
Merge commit: {pull_request.merge_commit_sha}
If action is 'closed' and pull_request.merged is true:
1. Fetch the diff: curl -sL {pull_request.diff_url}
2. Analyze what changed
3. Determine if this change needs to be ported to the Go SDK equivalent
4. If yes, create a branch, apply the equivalent changes, and open a PR on the target repo
5. Reference the original PR in the new PR description
If action is not 'closed' or not merged, respond with [SILENT]." \
--skills "github-pr-workflow" \
--deliver log
```
---
## Business Operations
### Stripe Payment Monitoring
Track payment events and get summaries of failures.
**Trigger:** API call (webhook)
```bash
hermes webhook subscribe stripe-payments \
--events "payment_intent.succeeded,payment_intent.payment_failed,charge.dispute.created" \
--prompt "Stripe event received:
Event type: {type}
Amount: {data.object.amount} cents ({data.object.currency})
Customer: {data.object.customer}
Status: {data.object.status}
For payment_intent.payment_failed:
- Identify the failure reason from {data.object.last_payment_error}
- Suggest whether this is a transient issue (retry) or permanent (contact customer)
For charge.dispute.created:
- Flag as urgent
- Summarize the dispute details
For payment_intent.succeeded:
- Brief confirmation only
Keep responses concise for the ops channel." \
--deliver slack
```
### Daily Revenue Summary
Compile key business metrics every morning.
**Trigger:** Schedule (daily)
```bash
hermes cron create "0 8 * * *" \
"Generate a morning business metrics summary.
Search the web for:
1. Current Bitcoin and Ethereum prices
2. S&P 500 status (pre-market or previous close)
3. Any major tech/AI industry news from the last 12 hours
Format as a brief morning briefing, 3-4 bullet points max.
Deliver as a clean, scannable message." \
--name "Morning briefing" \
--deliver telegram
```
---
## Multi-Skill Workflows
### Security Audit Pipeline
Combine multiple skills for a comprehensive weekly security review.
**Trigger:** Schedule (weekly)
```bash
hermes cron create "0 3 * * 0" \
"Run a comprehensive security audit of the hermes-agent codebase.
1. Check for dependency vulnerabilities (pip audit, npm audit)
2. Search the codebase for common security anti-patterns:
- Hardcoded secrets or API keys
- SQL injection vectors (string formatting in queries)
- Path traversal risks (user input in file paths without validation)
- Unsafe deserialization (pickle.loads, yaml.load without SafeLoader)
3. Review recent commits (last 7 days) for security-relevant changes
4. Check if any new environment variables were added without being documented
Write a security report with findings categorized by severity (Critical, High, Medium, Low).
If nothing found, report a clean bill of health." \
--skills "codebase-security-audit" \
--name "Weekly security audit" \
--deliver telegram
```
### Content Pipeline
Research, draft, and prepare content on a schedule.
**Trigger:** Schedule (weekly)
```bash
hermes cron create "0 10 * * 3" \
"Research and draft a technical blog post outline about a trending topic in AI agents.
1. Search the web for the most discussed AI agent topics this week
2. Pick the most interesting one that's relevant to open-source AI agents
3. Create an outline with:
- Hook/intro angle
- 3-4 key sections
- Technical depth appropriate for developers
- Conclusion with actionable takeaway
4. Save the outline to ~/drafts/blog-$(date +%Y%m%d).md
Keep the outline to ~300 words. This is a starting point, not a finished post." \
--name "Blog outline" \
--deliver local
```
---
## Quick Reference
### Cron Schedule Syntax
| Expression | Meaning |
|-----------|---------|
| `every 30m` | Every 30 minutes |
| `every 2h` | Every 2 hours |
| `0 2 * * *` | Daily at 2:00 AM |
| `0 9 * * 1` | Every Monday at 9:00 AM |
| `0 9 * * 1-5` | Weekdays at 9:00 AM |
| `0 3 * * 0` | Every Sunday at 3:00 AM |
| `0 */6 * * *` | Every 6 hours |
### Delivery Targets
| Target | Flag | Notes |
|--------|------|-------|
| Same chat | `--deliver origin` | Default — delivers to where the job was created |
| Local file | `--deliver local` | Saves output, no notification |
| Telegram | `--deliver telegram` | Home channel, or `telegram:CHAT_ID` for specific |
| Discord | `--deliver discord` | Home channel, or `discord:CHANNEL_ID` |
| Slack | `--deliver slack` | Home channel |
| SMS | `--deliver sms:+15551234567` | Direct to phone number |
| Specific thread | `--deliver telegram:-100123:456` | Telegram forum topic |
### Webhook Template Variables
| Variable | Description |
|----------|-------------|
| `{pull_request.title}` | PR title |
| `{issue.number}` | Issue number |
| `{repository.full_name}` | `owner/repo` |
| `{action}` | Event action (opened, closed, etc.) |
| `{__raw__}` | Full JSON payload (truncated at 4000 chars) |
| `{sender.login}` | GitHub user who triggered the event |
### The [SILENT] Pattern
When a cron job's response contains `[SILENT]`, delivery is suppressed. Use this to avoid notification spam on quiet runs:
```
If nothing noteworthy happened, respond with [SILENT].
```
This means you only get notified when the agent has something to report.

View File

@@ -153,6 +153,7 @@ const sidebars: SidebarsConfig = {
'guides/use-voice-mode-with-hermes',
'guides/build-a-hermes-plugin',
'guides/automate-with-cron',
'guides/automation-templates',
'guides/cron-troubleshooting',
'guides/work-with-skills',
'guides/delegation-patterns',