Skip to content

The agent that grows with you

feat(plugin-catalog): add hermes-windows-eventlog

Yicheng-Mark4e1ea532fab7
diff --git a/plugin-catalog/hermes-windows-eventlog.yaml b/plugin-catalog/hermes-windows-eventlog.yaml
new file mode 100644
index 00000000000..018769f8960
--- /dev/null
+++ b/plugin-catalog/hermes-windows-eventlog.yaml
@@ -0,0 +1,45 @@
+name: hermes-windows-eventlog
+repo: https://github.com/Yicheng-Mark/hermes-windows-eventlog
+sha: 42f938b928ed8893916ab3ecfa9bdc745ecb13f4
+description: >-
+ Answer "why did this process die" on Windows: three read-only tools over the Windows
+ Event Log. win_crash_events reads Application Error / Application Hang / Windows Error
+ Reporting / .NET Runtime records for a time window, decodes the exception code
+ (0xC0000005 -> ACCESS_VIOLATION and the other codes a debugger would name), reports the
+ faulting module, its path and the fault offset, and groups repeated crashes by app and
+ signature. Records are classified by provider as well as by event id, so unrelated
+ providers that reuse ids 1000 and 1001 for informational events are not reported as
+ crashes. win_shutdown_events reads the System log for Kernel-Power 41 unexpected
+ restarts, bugchecks decoded to names (0x9F -> DRIVER_POWER_STATE_FAILURE, accepting the
+ decimal form some providers emit), EventLog 6008 dirty shutdowns, 1074 operator-initiated
+ restarts with the process and comment, and the 6005/6006/12/13 start and stop markers.
+ win_eventlog_query is the general case: any channel, filtered by event ids, levels, an
+ exact provider name or a payload substring, returning structured records instead of raw
+ XML. Queries read newest-first and stop at the window start or at a 5000-record scan cap;
+ a call returns at most 200 records and marks truncated payload text. Channel names,
+ provider names and numeric filters are validated before anything is interpolated into the
+ query. Disclosure - this plugin reads the local Windows event logs and hands what it finds
+ to the model: application and faulting-module paths, exception codes and offsets, report
+ ids, service names and provider message text, which routinely includes user and machine
+ paths (C:\Users\<name>\...). Treat tool output like any other local diagnostic dump when
+ sharing it. It reads only the channels the current account may read - Security and some
+ operational logs answer with an access-denied error rather than any attempt to obtain
+ elevation - and it never writes to a log, clears one or configures a channel. Stdlib-only
+ (ctypes wevtapi plus xml.etree): no Python dependencies, no child processes, no network
+ calls, no file writes, no self-update. Windows only.
+maintainer: Yicheng-Mark
+tier: community
+category: tools
+requires_hermes: ">=0.21.4"
+docs_url: https://github.com/Yicheng-Mark/hermes-windows-eventlog#readme
+version: "0.1.0"
+platforms:
+- windows
+capabilities:
+ provides_tools:
+ - win_crash_events
+ - win_shutdown_events
+ - win_eventlog_query
+ provides_hooks: []
+ provides_middleware: []
+ requires_env: []