hermes-windows-disks

Answer "are this machine's disks healthy, and which volume is filling up" on Windows: one table of every physical disk (model, serial, SSD/HDD/SCM, bus - nvme, sata, usb -, size, the storage stack's health word, GPT or MBR, boot/system flags, partition count) and every volume (drive letter, label, file system, capacity, free space with its percentage and a verdict, fixed/removable/network/cd-rom, the disk a volume lives on, the UNC path behind a mapped drive); volumes without a drive letter (EFI, recovery) are hidden unless asked for. win_disk_detail reads one disk or volume - by drive letter, label, model, serial or disk number - with the health in words (warning, unhealthy, and "unknown", which the storage stack reports on a perfectly healthy NVMe while OperationalStatus says ok - both are shown), the partition layout decoded from its GUID type (efi system, microsoft reserved, basic data, windows recovery), each partition's size, offset and letter, the largest contiguous free extent, and a plain-word free-space verdict (under 5 percent critical, under 10 percent low). Use it for "why is the disk slow", "will this drive fail", "where did the space go". Read-only: the storage classes are queried in one PowerShell CIM session, nothing is defragmented, formatted, resized, checked or repaired; no writes, no elevation, no network calls of its own. Enum values arrive as numbers and are decoded in the plugin - a Chinese-language Windows 11 was verified never to reach the answer; the whole table answers in about two thirds of a second. The plugin declares no Python dependencies. Windows only. Disclosure - the tools report disk models, serial numbers, sizes, health words, partition layouts, volume labels, capacities and free space, and the UNC paths behind mapped drives, to the model; treat the output like the machine's own Disk Management page.

Yicheng-MarkToolsv0.1.0Updated 4 hours ago

About

hermes-windows-disks

Read-only disk and volume health tools for Hermes on Windows: what the storage
stack itself says about every disk and every volume, in one PowerShell CIM
session, with the numeric enums decoded into words.

Tools

`win_disk_table`

Answer "are this machine's disks healthy, and which volume is filling up":

every disk — model, serial, media (ssd / hdd / scm), bus (nvme, sata, usb,
…), size, the storage stack's health word, GPT or MBR, boot/system flags,
partition count
every volume — drive letter, label, file system, capacity, free space with
its percentage and a verdict (critical under 5 %, low under 10 %), drive type
(fixed / removable / network / cd-rom), the local disk a volume lives on, and
the UNC path behind a mapped network drive

Volumes without a drive letter (EFI system, recovery, WINRE) are hidden unless
include_letterless is set; kind narrows to disks or volumes; query filters
by model, serial, letter, label or file system. The notes call out every disk
that reports warning or unhealthy, the "unknown" health word (see below), and
every volume below 10 % free.

`win_disk_detail`

One disk or one volume in full, by target — a drive letter (C: or C), a
volume label, a disk model, a serial number, or a disk number (0, disk 0):

a volume — every fact above, the free-space verdict in words, and the
owning disk's health beside it; a network volume names its UNC path
a disk — health in words, the partition layout decoded from each
partition's GUID type (efi system, microsoft reserved, basic data, windows
recovery) with size, offset and letter, its volumes with their free space,
the largest contiguous free extent, and the spindle speed where there is one

The "unknown" health word

MSFT_PhysicalDisk.HealthStatus answered 0 (unknown) on the writing
machine's perfectly healthy NVMe — not a fault. When the word reads unknown,
both signals are shown: the health word and OperationalStatus (which said
ok), and the notes say exactly that.

Cost and reach

One PowerShell session per call (~0.6 s on the writing machine, one NVMe disk,
five partitions, four volumes). Read-only: the storage classes are queried and
nothing is defragmented, formatted, resized, checked or repaired; no writes, no
elevation, no network calls of its own, no Python dependencies. Windows only.

Install

Clone this directory into ~/.hermes/plugins/hermes-windows-disks (or
hermes plugins install), then:

hermes plugins enable hermes-windows-disks

Tests: python -m pytest from this directory (25 unit with fakes, 5 live on a
real machine).

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

More by Yicheng-Mark

15 plugins by Yicheng-Mark in the catalog.

Yicheng-Markhermes-dpapi-secretsResolve Hermes environment variables at startup from a single secret file encrypted with the Windows Data Protection API, instead of keeping provider keys in plaintext in .env or auth.json. Config is secrets.dpapi.map, an ENV_VAR -> store-name mapping (bare names or dpapi:// names) plus an optional file path (default <HERMES_HOME>/secrets.dpapi). The file is one DPAPI blob keyed by the current Windows user profile, so it is unreadable by another Windows account and worthless off the machine; it is written by the bundled CLI (python -m hermes_dpapi_secrets set NAME, value read from a prompt or stdin, never from argv) and only read at runtime. Mapped names that are missing or empty are skipped with a warning; a file that is not ours, a blob this user cannot decrypt, or a payload that is not a flat string map is reported as an error with nothing injected. Disclosure - this source decrypts a file for every Hermes process that enables it: resolved values become environment variables of the Hermes process and its children, exactly like .env entries, so anything that can read that environment can see them. User-scope encryption only (the machine-wide flag is never used and is not exposed), and the at-rest protection is a bar for backups, cloud sync and dotfiles, not a boundary against code already running as the same user. Stdlib-only (ctypes): no Python dependencies, no subprocesses, no network calls, no self-update. Windows only. Applying fetched values stays the orchestrator's job; the plugin never writes os.environ itself. Disclosure — decrypts a DPAPI-encrypted secret file (default <HERMES_HOME>/secrets.dpapi) at startup for every Hermes process that enables it, and the resolved values become environment variables of Hermes and its child processes like `.env` entries; the encryption is per Windows user and protects backups, cloud sync and copied files, not against other code running as the same user. Local only: no network calls, no subprocesses.Communitytools Yicheng-Markhermes-wincredResolve Hermes environment variables from the current user's Windows Credential Manager at startup, instead of keeping provider keys in plaintext in .env or auth.json. Config is secrets.wincred.map, an ENV_VAR -> generic-credential-target mapping (bare names or wincred:// names); each value is read with CredReadW in the current user's vault and handed to the secret-source orchestrator, which applies it with the usual precedence, provenance and conflict rules. Values may be UTF-8 or UTF-16LE (cmdkey and the Credential UI write UTF-16); anything that does not decode to text, or that contains interior NULs, is skipped with a warning instead of being injected as a mangled key. Disclosure - this source reads your Windows Credential Manager: only the generic credentials named in the map, with no enumeration of the vault. Resolved values become environment variables of the Hermes process and its children, exactly like .env entries, so anything that can read that environment can see them. The package is read-only and stdlib-only (ctypes): it never creates, updates or deletes credentials, writes no files, starts no subprocesses, makes no network calls and does not self-update. Windows only. Credential Manager is user-scoped, so this raises the at-rest bar for backups, cloud sync and dotfiles; it is not a boundary against code already running as the same user. Applying fetched values stays the orchestrator's job; the plugin never writes os.environ itself. Disclosure — when enabled, reads only the Windows Credential Manager generic credentials named in secrets.wincred.map (no vault enumeration) and injects them as environment variables of the Hermes process and its children, exactly like .env entries; read-only, stdlib ctypes, no subprocesses, no network, no file writes; user-scoped at-rest protection, not a boundary against code already running as the same user.Communitytools Yicheng-Markhermes-windows-appsAnswer "what is installed on this Windows machine": the software inventory behind Apps & Features, swept straight from the four Uninstall registry keys (the machine's 64-bit and 32-bit views plus the user's), so a program is found even when the Settings page hides it - a per-user install that never shows on the machine page came from the user view on the writing machine. Each row carries version, publisher, size in MB, install date and which view it lives in; the same DisplayName in two views is a 32/64-bit dual install, marked instead of listed twice. Entries the publisher asked to hide (runtime packages, update rollups) are filtered out unless asked for. Details one program with every field its publisher wrote and a reading of the uninstall command (MSI product code, setup executable, appx, script) so the next step is known before anything is run; the install folder is checked against disk. Use it for "what did that installer actually register", for inventory before a cleanup, and for "which of the two installs does uninstalling remove". Read-only: registry keys are enumerated and uninstall strings are reported, never run; no network, no file writes, no elevation. The sweep is pure registry - 102 entries in seven milliseconds on the writing machine, the whole table in ten, no PowerShell, no WMI. The plugin declares no Python dependencies. Windows only. Disclosure - the tools report program names, versions, publishers, sizes, install folders and uninstall commands, and what is hidden from Apps & Features, to the model; treat the output like the machine's own Apps & Features page.Communitytools Yicheng-Markhermes-windows-devicesAnswer "which device on this Windows machine is unhappy, and what does it need" on Windows: win_device_table lists every present PnP device with its class (System, Net, HIDClass, Display), its status, its manufacturer, its stable device id, and its problem code in words - 28 is one with no driver installed, 10 one that cannot start, 43 one Windows stopped after it reported a failure, 22 one the person switched off on purpose and is not broken - filtering by name or id substring, by class, or to the devices that need attention; devices no longer plugged in are history, left out unless asked for. win_device_detail takes one device by id or name substring and adds the driver behind it from the signed-driver table - name, version, date, provider, signer, INF file, signed or not - or the absence of one, which for code 28 is the same fact said twice; a disabled device gets a note saying it is on purpose, not an alarm. Use it for the Device Manager yellow-mark question without opening Device Manager, for finding what an uninstalled program left behind, and for what changed after an update. Read-only: nothing is enabled, disabled, updated or reinstalled. Both answers come from CIM (Win32_PnPEntity and Win32_PnPSignedDriver, joined by device id), whose property names, enum values and ids do not change with the display language; the human-facing device names localize and are carried through as data, never parsed. The plugin declares no Python dependencies; there is no network call and no file write. Windows only. Disclosure — the tools report device names, manufacturers, device ids and driver versions to the model, and those reveal the machine's hardware inventory and what is plugged into it; treat the output like a Device Manager window opened on their machine.Communitytools

All 15 by Yicheng-Mark

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section