All plugins

deadline-guard

Deadline governance for Hermes. Reads a local Markdown deadlines table and exposes check_deadlines, next_founder_steps, propose_status_update, and deadline_guard_cron: commitments are bucketed overdue / 24h / 72h / 7d, founder-gated next steps are surfaced before they go critical, and a status can never be recorded as 'submitted' without an http(s) receipt URL - the proposal comes back unapplied for a human to confirm. Ships a daily-check automation blueprint (08:00 cron) and a bundled deadline-guard skill. Validated on Hermes 0.23.0: hermes plugins validate --install-deps exit 0, all 15 checks pass; 47 tests pass. Disclosure - stdlib only, no network calls, no model calls, no telemetry; reads only the configured local deadlines file (config deadlines_path, default examples/hackathon-deadlines.md); writes nothing itself. Disclosure — stdlib only, no network calls, no model calls, no telemetry; reads the configured local deadlines file (config deadlines_path, default examples/hackathon-deadlines.md) or a path the agent passes to a tool; the deadline_guard_cron install action writes an executable daily-check script to HERMES_HOME/scripts/deadline_guard_daily.py, which you attach yourself with hermes cron add; status updates are only proposed, never written.

SnedzAutomationv0.1.7Updated 6 hours ago

About

Deadline governance for Hermes. Reads a local Markdown deadlines table and exposes check_deadlines, next_founder_steps, propose_status_update, and deadline_guard_cron: commitments are bucketed overdue / 24h / 72h / 7d, founder-gated next steps are surfaced before they go critical, and a status can never be recorded as 'submitted' without an http(s) receipt URL - the proposal comes back unapplied for a human to confirm. Ships a daily-check automation blueprint (08:00 cron) and a bundled deadline-guard skill. Validated on Hermes 0.23.0: hermes plugins validate --install-deps exit 0, all 15 checks pass; 47 tests pass. Disclosure - stdlib only, no network calls, no model calls, no telemetry; reads only the configured local deadlines file (config deadlines_path, default examples/hackathon-deadlines.md); writes nothing itself. Disclosure — stdlib only, no network calls, no model calls, no telemetry; reads the configured local deadlines file (config deadlines_path, default examples/hackathon-deadlines.md) or a path the agent passes to a tool; the deadline_guard_cron install action writes an executable daily-check script to HERMES_HOME/scripts/deadline_guard_daily.py, which you attach yourself with hermes cron add; status updates are only proposed, never written.

deadline-guard (Hermes plugin)

Hermes plugin for markdown deadline tables: scan for ERROR/WARN conditions, list upcoming founder-only steps, and block “submitted” status without an http(s) receipt link.

Built for the Nous Hermes Agent Plugin Hackathon. Public MIT source: Snedz/hermes-deadline-guard.

Disclosure

  • Local file read only — reads the markdown path you configure (deadlines_path). No network calls, no shell, no secrets.
  • Default demo data — examples/hackathon-deadlines.md uses fictional rows only.
  • Does not edit your table by default — propose_status_update validates; you apply changes in git or your editor.
  • Cron — optional daily script writes under $HERMES_HOME/scripts/ when you use deadline_guard_cron action install.

Install (Hermes)

INSTALL.md — clean checkout verify (python3 install_smoke.py), config, and Hermes install.

hermes plugins install /path/to/hermes-deadline-guard
hermes plugins validate /path/to/hermes-deadline-guard --install-deps

Set deadlines_path in plugin config to your table (absolute path or relative to the plugin directory). Empty config falls back to examples/hackathon-deadlines.md; missing files return a clear deadlines_path hint in tool JSON.

Tools

ToolPurpose
check_deadlinesERROR/WARN scan (missing owner, past due, founder step due ≤3 days, etc.)
next_founder_stepsRows with founder-step-by inside within_hours (default 48)
propose_status_updateValidates status; requires receipt URL for submit-like statuses
deadline_guard_cronrun — summary now; install — stdlib script for hermes cron --script

Demo (judges)

INSTALL.md — one-command verify. Step-by-step replay: DEMO.md. Kitchen <90 s video: see DEMO_VIDEO.md and bash demo/run_demo.sh (not in the public export).

python3 install_smoke.py
python3 -m unittest discover -s tests -v
python3 demo_cli.py

Kitchen staging adds python3 judge_path.py (includes sync_lint); see JUDGE.md (not shipped in the public export).

Tests (stdlib unittest)

From the plugin root (directory containing plugin.yaml):

python3 -m unittest discover -s tests -v
python3 manifest_lint.py
python3 catalog_lint.py    # kitchen catalog YAML; skips with exit 0 on public clone (no plugin-catalog/)
python3 sync_lint.py       # plugin.yaml version/tools must match catalog draft
python3 export_public.py --check   # forbidden kitchen strings + public doc link scan

Table format

First markdown table in the file, with columns: Item, Owner, Deadline ET, Build window, Planned build blocks, Founder-only step, Founder step by, Link, Status.

Publish (maintainers)

Before tagging a public release, confirm the export manifest is clean:

python3 export_public.py --json > /tmp/deadline-guard-manifest.json
python3 export_public.py --check

Copy every path listed in the manifest, run hermes plugins validate . --install-deps, tag, then pin the tag SHA in the Hermes plugin catalog (kitchen staging holds plugin-catalog/deadline-guard.yaml).

License

MIT — see LICENSE.

README from the reviewed commit e79b9e9; it updates when the author re-pins.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section