Готовые рецепты для типовых сценариев автоматизации. Каждый шаблон использует встроенный планировщик cron для временных триггеров и платформу webhook для событийных триггеров.
Каждый шаблон работает с любой моделью — не привязан к одному провайдеру.
cronjob или слэш-команда /cron |
| GitHub Event | Срабатывает при открытии PR, пушах, issues, результатах CI | Платформа webhook (hermes webhook subscribe) |
| API Call | Внешний сервис отправляет JSON на ваш endpoint | Платформа webhook (маршруты в config.yaml или hermes webhook subscribe) |
Все три типа поддерживают доставку в Telegram, Discord, Slack, SMS, email, комментарии GitHub или локальные файлы.
Маркируйте, приоритизируйте и обобщайте новые задачи каждую ночь. Доставляет дайджест в ваш командный канал.
Триггер: Расписание (каждую ночь)
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
Автоматически проверяйте каждый pull request при его открытии. Публикует комментарий с ревью прямо в 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." \\
--skill 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
Запускайте smoke-тесты после каждого развёртывания. Ваш CI/CD pipeline отправляет POST на webhook, когда деплой завершён.
Триггер: API call (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 pipeline запускает его:
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 call (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
Проверяйте endpoints каждые 30 минут. Уведомляйте только когда что-то недоступно.
Триггер: Расписание (каждые 30 мин)
```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
Отслеживайте интересные 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." \\
--skill competitive-pr-scout \\
--name "Competitor scout" \\
--deliver telegram
Еженедельный обзор событий в мире 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." \\
--skill arxiv --skill obsidian \\
--name "Paper digest" \\
--deliver local
Автоматически маркируйте и отвечайте на новые issues.
Триггер: 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 и публикуйте диагностику в 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]." \\
--skill github-pr-workflow \\
--deliver log
Отслеживайте платежные события и получайте сводки об ошибках.
Триггер: API call (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." \\
--skill 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
| Выражение | Значение |
|---|---|
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:+155****4567 |
Напрямую на номер телефона |
| Конкретная тема | --deliver telegram:-100123:456 |
Тема форума Telegram |
| Переменная | Описание |
|---|---|
{pull_request.title} |
Название PR |
{issue.number} |
Номер issue |
{repository.full_name} |
owner/repo |
{action} |
Действие события (opened, closed и т.д.) |
{__raw__} |
Полный JSON payload (обрезано до 4000 символов) |
{sender.login} |
Пользователь GitHub, вызвавший событие |
Если ответ cron-задачи содержит [SILENT], доставка подавляется. Используйте это, чтобы избежать спама уведомлениями при пустых запусках:
If nothing noteworthy happened, respond with [SILENT].
Это означает, что вы получите уведомление только тогда, когда агенту есть что сообщить.