GitHub profilePlugins by am423
2 plugins by am423 in the catalog, most-starred first.
am423hermes-verifierAttach an independent verifier (advisor) model to your Hermes session: it reviews each primary-agent turn delta, raises findings (note / caution / blocker), and can steer a blocker back into the session before the primary agent goes wrong. Read-only tool access (read_file, search_files) is available but off by default and best treated as opt-in plumbing -- measured across 216 reviews the reviewer made ~4 tool calls. Supports a VERIFIER.yml roster of named specialists, each with its own model and tool grant, plus VERIFIER.md review priorities. Ships disabled and off by default. Disclosure — off by default. When enabled, each primary turn's regex-redacted transcript delta goes to the verifier model's provider on that provider's terms and billing (one or more calls per turn per roster entry). So do any VERIFIER.md / VERIFIER.yml briefs found in HERMES_HOME and from the working directory up to the repo root (confined to that root, 256 KiB per file). A project VERIFIER.yml can add named verifiers and instructions whose findings are injected into your session, and a blocker finding can keep a coding turn going. With advisor_tools on, an advisor can read any file the session can read through read_file/search_files, and those reads also go to the provider. The optional engagement gate sends a ≤1,500-char redacted digest per turn. The optional phase gate sends the redacted arguments of an impending destructive or publishing tool call and can block that call (it fails open). Findings, reasoning, short redacted excerpts and gate decisions are logged under HERMES_HOME/plugin-data/hermes-verifier (rotated at 8 MB). Adds a /verify command, a dashboard API and a Desktop Verifier page. Development scripts (evals/, sidecar/, autoresearch/) run only when launched by hand: provider experiments use DEEPSEEK_API_KEY from the process environment or the host `hermes` CLI, and offline analysis reads the active profile's session database and decision logs. No telemetry, no runtime shell execution, no access to Hermes's stored credentials.Communitytools2am423hermes-r0b0t-vibecadProfile-driven FDM CAD: executes trusted build123d workspace models or prepares a local single-shell STL, checks printer fit, renders depth-tested full and detail views, and writes geometry handoffs. Bambu adapters cover X2D and P2S; native process projects, live AMS binding and print dispatch are not produced. Meshy is an optional separate plugin; its paid service calls are not made by vibeCAD. CAD libraries require a separately bootstrapped Python 3.12/3.13 environment. Disclosure: reads/writes workspace files and runs trusted Python in a local subprocess. Agent execution requires approval of the final script path and bytes; direct runtime calls bypass the agent gate. The subprocess environment is minimized, not a sandbox: approved code can access files, credentials and the network. Approval binds only the top-level script. Internal Hermes approval and interrupt APIs may change and produce catalog rule 9 warnings. The plugin itself makes no runtime network calls or telemetry.Communitytools
