asimons81/hermes-field-kit

Use when the user explicitly wants evidence-disciplined answers that separate observed facts, sourced claims, user reports, inference, unknowns, and contradictions before making strong factual or completion claims.

Safely migrate Hermes environments between machines with staged exports, integrity verification, secret separation, selective imports, and rollback support.

A toolkit for deploying and managing Hermes AI agents in field environments, providing reusable components and workflows for robust agent operations.

Diagnose Hermes messaging gateway failures by inspecting process state, adapters, credentials, logs, delivery evidence, and conflicts without automatic repair.

Conducts a read-only audit of a Hermes agent profile, comparing declared role to actual tools, skills, access, and behavior, to identify misalignments without automatic rewriting. Produces an evidence-based improvement plan.

A read-only audit tool for installed Hermes skills that identifies overlaps, staleness, broken references, and usage integrity issues without making changes.

Safely consolidate, restructure, deprecate, split, or share references across installed Hermes skills after overlap is established. Generates a read-only plan with rollback snapshots, staged writes, and post-change verification before any mutation.

Performs a comprehensive read-only health audit of a Hermes agent stack, covering installation, gateways, cron jobs, profiles, skills, and persistence, producing a GREEN/YELLOW/RED verdict.

Read-only, schema-discovering token and cost audit for Hermes, separating local estimates from provider billing. Investigate runaway sessions, cron consumption, and billing discrepancies with privacy-preserving evidence.

Diagnose stuck, contradictory, or incomplete Hermes updates by inspecting Git state, processes, caches, and installed versions before recovery. Evidence-first, read-only by default.

Conducts an adaptive, one-question-at-a-time interview to clarify goals, constraints, and preferences before starting work. It inspects available sources first, avoids repeating known information, and stops when more questions wouldn't change the next action.

Perform an evidence-driven trust audit of open-source developer tools to assess legitimacy, supply-chain risks, telemetry, dangerous capabilities, and adoption fit before use.

Performs a read-only audit across source code, history, branches, issues, pull requests, roadmaps, and contributor guidance to ensure a feature hasn't already been implemented or is in progress before starting development.

Performs a disciplined, read-only audit of a Git repository to determine if it is ready for further development, release, handoff, or a new contributor, producing an evidence-backed verdict without modifying anything.

Use when X Analytics CSV exports must be inspected, validated, normalized, imported, or compared through a repeatable private-by-default workflow.

Use when drafting, rewriting, or repurposing short-form X content, including single posts, quote posts, replies, threads, launches, and personal stories, with source fidelity and claim verification built in.