All plugins

photo-to-part

Photo to Part for Hermes: turn photos, a few measurements, or a messy 3D scan into a parametric printable part, and check the mesh locally before you print. The agent writes the solid in code, checks that it is watertight and the right size, and renders views you can hold next to the original. Six tools: photo_part_template (watertight starting shapes such as plates with holes, an L-bracket, a print-in-place hinge, thread, knurl, hex standoff, bottle cap, spur gear and strap hinge), photo_part_build (runs one local build script after Hermes approval), photo_part_validate (watertightness, shell count, size, bores, printability and spec.json dimension checks), photo_part_render (fitted views, a comparison sheet and a silhouette overlay scored against your photo), photo_part_heal (weld, fill holes and clean up a scan) and photo_part_measure (pixels per millimetre from a coin, a ruler or an ArUco/AprilTag marker). Output is STL or 3MF; a STEP solid needs CadQuery or build123d in the project environment. A millimetre value you state is never replaced by a photo measurement. Hermes Desktop 0.23 or newer can show an optional Part studio pane with the stage, photo and overlay, renders, history and file paths while a run is in progress; the six tools still install and run when that pane is unavailable. It is for makers replacing a broken clip, bracket, knob, cap or gear, printing a fit test, or turning a scan into a clean solid. To start, run hermes plugins install photo-to-part and enable it, then start a new session. Attach a photo with a coin or ruler in frame, give any dimensions you know, and ask for a printable replacement. The skill id is photo-to-part:photo-to-printable-part. Pass that exact string only to skill_view. Do not pass it to skills_list, and do not add a plugin: prefix or a slash. Disclosure — files and network: tools read and write only the paths you pass (STL, 3MF, PNG, JSON), plus progress notes in a .photopart folder inside those project folders and a pane index under the Hermes plugin-data folder. Build scripts run with a minimal environment that carries no provider keys. No credentials and no printer connection. Enabling the plugin installs its Python packages from PyPI after Hermes dependency consent. Installing CadQuery or build123d for a STEP solid downloads packages and can take several minutes. Chat photos still go to your model provider. In a session that uses the plugin, it adds short tool-call budget notes (a 40-call default) to other tools' results. Disclosure — build approval: photo_part_build asks for approval before it runs a local Python file with a timeout. Hermes --yolo auto-approves a build prompt; this plugin does not block that flag.

mojomast5Toolsv0.1.23Updated 7 days ago

About

Photo to Part for Hermes: turn photos, a few measurements, or a messy 3D scan into a parametric printable part, and check the mesh locally before you print. The agent writes the solid in code, checks that it is watertight and the right size, and renders views you can hold next to the original. Six tools: photo_part_template (watertight starting shapes such as plates with holes, an L-bracket, a print-in-place hinge, thread, knurl, hex standoff, bottle cap, spur gear and strap hinge), photo_part_build (runs one local build script after Hermes approval), photo_part_validate (watertightness, shell count, size, bores, printability and spec.json dimension checks), photo_part_render (fitted views, a comparison sheet and a silhouette overlay scored against your photo), photo_part_heal (weld, fill holes and clean up a scan) and photo_part_measure (pixels per millimetre from a coin, a ruler or an ArUco/AprilTag marker). Output is STL or 3MF; a STEP solid needs CadQuery or build123d in the project environment. A millimetre value you state is never replaced by a photo measurement. Hermes Desktop 0.23 or newer can show an optional Part studio pane with the stage, photo and overlay, renders, history and file paths while a run is in progress; the six tools still install and run when that pane is unavailable. It is for makers replacing a broken clip, bracket, knob, cap or gear, printing a fit test, or turning a scan into a clean solid. To start, run hermes plugins install photo-to-part and enable it, then start a new session. Attach a photo with a coin or ruler in frame, give any dimensions you know, and ask for a printable replacement. The skill id is photo-to-part:photo-to-printable-part. Pass that exact string only to skill_view. Do not pass it to skills_list, and do not add a plugin: prefix or a slash. Disclosure — files and network: tools read and write only the paths you pass (STL, 3MF, PNG, JSON), plus progress notes in a .photopart folder inside those project folders and a pane index under the Hermes plugin-data folder. Build scripts run with a minimal environment that carries no provider keys. No credentials and no printer connection. Enabling the plugin installs its Python packages from PyPI after Hermes dependency consent. Installing CadQuery or build123d for a STEP solid downloads packages and can take several minutes. Chat photos still go to your model provider. In a session that uses the plugin, it adds short tool-call budget notes (a 40-call default) to other tools' results. Disclosure — build approval: photo_part_build asks for approval before it runs a local Python file with a timeout. Hermes --yolo auto-approves a build prompt; this plugin does not block that flag.

photo-to-part plugin

This directory is what Hermes installs:

hermes plugins install mojomast/hermes-photo-to-part/plugin --no-enable

Version 0.1.23. The repository README, changelog, security notes, evals, and tests live one directory up and are not part of this install. From this directory, hermes plugins doctor . reports the six photo_part_* tools.

Hermes Desktop 0.23 or newer loads desktop/plugin.js as an optional Part studio pane. It reads /api/plugins/photo-to-part/ from dashboard/plugin_api.py. The pane is not a tool. Older Hermes builds ignore those files and keep the six tools.

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

More by mojomast

13 plugins by mojomast in the catalog.

mojomastaircraft-doppler-geolocationDetect aircraft flyovers in a recording (Doppler tones, plus experimental ground-reflection broadband jet passes) and estimate where it was made by scoring them against adsb.lol ADS-B history, with a posterior heatmap, 68/95% areas and a confidence flag. Provides the doppler_detect and doppler_locate tools and a dopplergeo CLI. Results on unseen real recordings are weak (2 of 18 held-out runs under 3 km); treat output as a hypothesis. Disclosure — doppler_locate / dopplergeo locate makes unauthenticated HTTPS GETs to GitHub (adsb.lol release assets, streamed, about 3 GB read per uncached day; only the crop is cached), raw.githubusercontent.com (tar1090-db types), the Copernicus DEM S3 bucket and Open-Meteo, caching results under ~/.cache/doppler-geo (or DOPPLER_GEO_CACHE); offline mode uses the local cache only; no credentials, uploads or telemetry. doppler_detect and the skill scripts make no network calls; the tools and scripts run ffmpeg/ffprobe (no shell) on the recording you name and write CSV/PNG/JSON at the output path you give (default <recording>.doppler/). PyPI packages (numpy, scipy, soundfile, matplotlib, tifffile) install only after Hermes dependency consent. The method can geolocate where a recording was made, so use it only on recordings you are entitled to analyse.Communitytools18mojomastgodseyeEye Of Hermes (EOH) puts a live 3D globe beside your Hermes chat that the agent can fly, read, annotate and watch. It is built on God's Eye View (bilawalsidhu/gods-eye-view, MIT). Eleven composable tools (godseye_view, godseye_query, godseye_layers, godseye_feeds, godseye_annotate, godseye_nav, godseye_track, godseye_scene, godseye_watch, godseye_capture, godseye_admin) work on public data (aircraft, ships, satellites, earthquakes, fires, weather, infrastructure and public SDR receivers) and drive the pane in Hermes Desktop and the Webapp. The agent can fly to a place and switch the visual style (night vision, thermal, noir and others); answer "what am I looking at" from the camera, the open pin or your last click; search for places and pin them with research drawers and an attached YouTube or X clip; measure distances and areas and draw walk, bike and drive routes and reach isochrones; compare imagery before and after with Esri Wayback and replay earthquakes and fires on a time slider; walk a route in Street View; follow a public aircraft, ship or satellite by its identifier; play Director camera scenes; leave area watches that report new items on the next chat turn; and save an investigation as an HTML or Markdown report, GeoJSON or KML. The Overlays sidebar lists pins, routes, areas, watches and scenes and imports or exports eoh.overlays.v1 JSON. HUD summaries use your Hermes model (ctx.llm), not OpenAI. Use it for situation briefs on a region, place and travel research, checking a fire or an earthquake, and any answer that is clearer on a map. To start, you need Hermes 0.23.0 or newer, Node 24 or newer (God's Eye View documents 24.14 or later, or 26.x) and a running God's Eye View checkout; the public SDR layer needs gods-eye-view main at or after b361a25. Run hermes plugins install godseye, hermes plugins enable godseye and hermes plugins doctor godseye, open the Eye Of Hermes pane, and start a new chat. Try "Fly to Tokyo and switch to night vision" or "Any earthquakes above magnitude 5 in the last day?" (data questions work with the pane closed). The bundled skill is godseye:godseye-analyst. Photorealistic 3D tiles need CESIUM_ION_TOKEN, live ships need AISSTREAM_API_KEY and fires need FIRMS_MAP_KEY; the Google Maps, Mapillary and TomTom keys are optional. Set them as Hermes secrets. Named-person search, face recognition and tracking of individuals are refused. Disclosure — processes: starts one node MCP child from your God's Eye View checkout, plus git rev-parse, node and systemctl --user children, all with a minimal environment. godseye_admin app_start, app_stop, app_restart and rebuild require confirm=true, are refused inside batch, may run systemctl --user on gods-eye-view.service, start Node on the checkout's vite.js, or run npm run build:panel in the checkout, and refuse a foreign listener. Disclosure — background work and prompt: runs loopback-only HUD bridge (127.0.0.1:18791) and live relay (127.0.0.1:18792) threads gated by a random token stored 0600 in plugin-data; registers a godseye.live-globe system-prompt section and ships the godseye-analyst skill; a pre_llm_call hook may add a short map line and queued watch alerts, whose feed titles are passed as quoted third-party text; an active area watch polls USGS, NASA FIRMS, OpenSky (falling back to api.adsb.lol when OpenSky fails), the local app, or Overpass/Nominatim from a daemon thread. Disclosure — network: place search, routes, isochrones, Wayback metadata and pin research call public services (Nominatim, Overpass and public Overpass mirrors, OSRM, Valhalla, Esri, Wikipedia, Wikidata, Wikimedia and venue sites), and private-LAN service URLs are refused. Feed tools, including fire_check, and godseye_query op=sdr_receivers talk to your God's Eye View app, which itself fetches public third-party data feeds and the public SDR receiver directory. Disclosure — credentials: all provider credentials are declared in plugin.yaml requires_env and read only through agent.secret_scope.get_secret; no plugin dotenv reads, key-file installation or process-wide credential mutation. Browser-facing credentials are written only to gitignored mode-0600 runtime config, and server-only secrets never enter the pane. Disclosure — files and pane: overlay import and export stay under plugin-data/godseye/overlays and are not uploaded, and credential-named files are refused for import. Opening a pin drawer that has a clip loads a www.youtube-nocookie.com/embed or platform.twitter.com/embed iframe inside the sandboxed frame. Pane link opens and Ask Hermes run only after a click on the pane's confirm bar. The pane backend adds a base tag, an opt-in UI flag, a Cesium worker shim, the overlay sidebar and Director bridge scripts, and the live agent script inside the sandboxed frame only.Communitytools10mojomastorbit-desktopYour workspace, shaped by your agent: a bundled browser desktop powered by Hermes. Describe the workflow you need; the agent can rearrange windows and panes, customize appearance, build versioned sandboxed web apps, and refine your workspace with scoped control, previews and checkpoints. Illustrated examples show a project-specific COCS 3D asset viewer and OmniVoice experiment bench; these example apps and their backends are not bundled. Includes permission-controlled desktop agent-reply notifications (generic alerts while Orbit remains open; browser/OS restrictions apply) and 100,000-character chat messages, guidance and drafts. Includes Devplan Studio for guided interviews, specifications, phased devplans and circular-development handoff exports. Optional conversational interviews require explicit service setup and a working Hermes provider login, and send project context to that provider. Includes 14 distinctive interface presets including Nous Atelier, with local wallpapers, themed icons and taskbar treatments. Agent chats include inline expandable tool activity, running/completed/failed summaries, an activity strip, a workspace agent overview and responsive toolbar controls. Missing tool-call IDs are explicitly uncorrelated. Embedded apps retain their own styling. Includes a reviewed GitHub app catalog with immutable source pins and a portable Live Telemetry package. Catalog sync (operator-run scripts/orbit_catalog.py, never triggered by the Hermes tool or at register) reads the entry list from the upstream repo's main branch at sync time and downloads third-party static app bundles at their per-entry commit pins; installed UI runs in a sandboxed iframe and never executes backend code. Optional telemetry backend staging downloads pinned Python; execution requires explicit host-code trust and separate private authenticated HTTPS setup. Backend code runs with owner privileges, not a sandbox. Disclosure — adapter talks only to the configured local Orbit server (loopback, Bearer capability from runtime_dir); mutations off by default. Optional orbit.py setup runs npm ci / node. Bundled VNC/Xpra launchers use the Orbit page's hostname and scheme; optional Linux apps require separate provisioning. Optional api.typesafe.ai requests require explicit consent and a user-supplied key. The 0.2.7 web app's opt-in Show tools panel displays tool call arguments and results for the current Hermes conversation, fetched from the local Orbit server and local Hermes session API and kept in the browser only. The Nous Atelier theme contains Nous Research logo artwork and is unofficial; Orbit is not affiliated with Nous Research.CommunityDesktop app10mojomasthyperrizzHyperrizz: tell Hermes the story and watch your HyperFrames film take shape in a live review pane, then get a verified MP4. Hermes researches, art-directs, writes the scenes, builds, checks and iterates on a HyperFrames project while the pane plays the actual composition with sound, a scrubber and frame stepping. Pause on a moment, write a note and press Iterate with Hermes: the note carries the project, revision and exact frame back into the chat. Full editor opens HyperFrames Studio inside the pane (timeline, assets, code, layers, inspector), and the agent reconciles your manual edits before it rebuilds. Renders are separate, cancellable jobs; a failed build keeps the last working revision and a failed export keeps the last verified MP4. Three tools: hyperrizz_project (create, inspect, edit, restore and reconcile projects), hyperrizz_review (open the pane, exchange frame notes, hand off to Studio) and hyperrizz_produce (build, check, render, inspect jobs, cancel), plus the hyperrizz:production skill with its guides, a broadcast kit and starter templates. Use it for product promos, release announcements, music-led cuts, and restyling or rescuing an existing film. To start, you need Hermes 0.23.0 or newer, Node 22 or newer, Python 3.11 or newer and FFmpeg; Linux is the tested platform. Run hermes plugins install hyperrizz and hermes plugins enable hyperrizz, enable Hyperrizz under Capabilities → Plugins to show the pane, then ask: "Use Hyperrizz to make a 30-second film about this release. Show the live project as you work, then deliver the MP4." The first build installs the pinned npm dependencies. No API keys or hosted generation. Disclosure — processes: spawns local Node, Chromium and FFmpeg child processes with a minimal non-secret environment; runs background build, check and render workers and an optional loopback Studio sidecar (token-gated, 512 KiB capture budget, no redirects); the embedded HyperFrames Studio server listens on loopback without a token. Disclosure — code execution: project write can edit the project's scripts/*.mjs and package.json, and build, check and render run them with Node at your full privileges (no filesystem or network sandbox), the same power as file writes plus the terminal. npm downloads pinned dependencies on first build, and npm ci runs package lifecycle scripts. Disclosure — data: projects are stored in profile-scoped plugin data; the Desktop pane uses ctx.rest only; a post_tool_call hook binds projects to the host session. No credentials, no telemetry, no self-update.CommunityDesktop app5

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section