自动化模板

常见自动化模式的即插即用配方。每个模板都使用 Hermes 内置的 cron 调度器进行基于时间的触发，以及 Webhook 平台进行事件驱动的触发。

每个模板都适用于任何模型——不锁定于单一提供商。

三种触发类型

触发器	方式	工具
计划任务	按节奏运行（每小时、每晚、每周）	`cronjob` 工具或 `/cron` 斜杠命令
GitHub 事件	在 PR 打开、推送、Issues、CI 结果时触发	Webhook 平台 (`hermes webhook subscribe`)
API 调用	外部服务向你的端点 POST JSON	Webhook 平台 (config.yaml 路由或 `hermes webhook subscribe`)

所有这三种方式都支持交付到 Telegram、Discord、Slack、SMS、电子邮件、GitHub 评论或本地文件。

开发工作流

夜间待办事项分类

每晚对新 Issue 进行标记、优先级排序和总结。将摘要发送到你的团队频道。

触发器： 计划任务（每晚）

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

自动 PR 代码审查

在每次拉取请求打开时自动进行审查。直接在 PR 上发布审查评论。

触发器： GitHub Webhook

选项 A — 动态订阅（CLI）：

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

选项 B — 静态路由（config.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}"

然后在 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。

文档漂移检测

每周扫描已合并的 PR，以查找需要更新文档的 API 变更。

触发器： 计划任务（每周）

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

依赖安全审计

每天扫描项目依赖项中的已知漏洞。

触发器： 计划任务（每天）

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 与监控

部署验证

在每次部署后触发冒烟测试。当部署完成时，你的 CI/CD 流水线向 Webhook 发送 POST 请求。

触发器： API 调用（Webhook）

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

你的 CI/CD 流水线触发它：

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"}'

告警分类

将监控告警与最近的变更关联起来以起草响应。适用于 Datadog、PagerDuty、Grafana 或任何可以 POST JSON 的告警系统。

触发器： API 调用（Webhook）

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

可用性监控

每 30 分钟检查一次端点。仅在出现故障时通知。

触发器： 计划任务（每 30 分钟）

~/.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")

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

研究与情报

竞争对手仓库侦察

监控竞争对手的仓库，了解有趣的 PR、功能和架构决策。

触发器： 计划任务（每天）

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 新闻摘要

每周汇总 AI/ML 发展动态。

触发器： 计划任务（每周）

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

带笔记的论文摘要

每日扫描 arXiv，将摘要保存到你的笔记系统中。

触发器： 计划任务（每天）

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 事件自动化

Issue 自动标记

自动标记并回复新 Issue。

触发器： GitHub Webhook

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 失败分析

分析 CI 失败并在 PR 上发布诊断信息。

触发器： GitHub Webhook

# 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}"

跨仓库自动移植变更

当一个 PR 在一个仓库中合并时，自动将等效变更移植到另一个仓库。

触发器： GitHub Webhook

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

业务运营

Stripe 支付监控

跟踪支付事件并获取失败摘要。

触发器： API 调用（Webhook）

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

每日收入摘要

每天早上编译关键业务指标。

触发器： 计划任务（每天）

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

多技能工作流

安全审计流水线

结合多种技能进行全面的每周安全审查。

触发器： 计划任务（每周）

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

内容流水线

按计划研究、起草和准备内容。

触发器： 计划任务（每周）

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

快速参考

Cron 调度语法

表达式	含义
`every 30m`	每 30 分钟
`every 2h`	每 2 小时
`0 2 * * *`	每天凌晨 2:00
`0 9 * * 1`	每周一上午 9:00
`0 9 * * 1-5`	工作日早上 9:00
`0 3 * * 0`	每周日凌晨 3:00
`0 /6 * *`	每 6 小时

交付目标

目标	标志	说明
相同聊天	`--deliver origin`	默认 — 发送到任务创建的位置
本地文件	`--deliver local`	保存输出，不发送通知
Telegram	`--deliver telegram`	主频道，或使用 `telegram:CHAT_ID` 指定特定频道
Discord	`--deliver discord`	主频道，或使用 `discord:CHANNEL_ID`
Slack	`--deliver slack`	主频道
SMS	`--deliver sms:+15551234567`	直接发送到电话号码
特定主题帖	`--deliver telegram:-100123:456`	Telegram 论坛主题

Webhook 模板变量

变量	描述
`{pull_request.title}`	PR 标题
`{issue.number}`	Issue 编号
`{repository.full_name}`	`owner/repo`
`{action}`	事件操作（opened、closed 等）
`{__raw__}`	完整 JSON 负载（截断至 4000 字符）
`{sender.login}`	触发事件的 GitHub 用户

[SILENT] 模式

当定时任务的响应包含 [SILENT] 时，将抑制发送。使用此功能可避免在静默运行时产生通知垃圾邮件：

If nothing noteworthy happened, respond with [SILENT].

这意味着只有当代理有内容需要报告时，您才会收到通知。

开发工作流​

夜间待办事项分类​

自动 PR 代码审查​

文档漂移检测​

依赖安全审计​

DevOps 与监控​

部署验证​

告警分类​

可用性监控​

研究与情报​

竞争对手仓库侦察​

AI 新闻摘要​

带笔记的论文摘要​

GitHub 事件自动化​

Issue 自动标记​

CI 失败分析​

跨仓库自动移植变更​

业务运营​

Stripe 支付监控​

每日收入摘要​

多技能工作流​

安全审计流水线​

内容流水线​

快速参考​

Cron 调度语法​

交付目标​

Webhook 模板变量​

[SILENT] 模式​

开发工作流

夜间待办事项分类

自动 PR 代码审查

文档漂移检测

依赖安全审计

DevOps 与监控

部署验证

告警分类

可用性监控

研究与情报

竞争对手仓库侦察

AI 新闻摘要

带笔记的论文摘要

GitHub 事件自动化

Issue 自动标记

CI 失败分析

跨仓库自动移植变更

业务运营

Stripe 支付监控

每日收入摘要

多技能工作流

安全审计流水线

内容流水线

快速参考

Cron 调度语法

交付目标

Webhook 模板变量

[SILENT] 模式