All plugins

mesh-check

Mesh Check reads one local STL, OBJ, PLY, GLB, or glTF file and returns whether it is closed, its volume, its bounds, and mesh, animation, and material counts. Use it before a 3D print or a game export. Disclosure — reads any local file path the agent passes (following symlinks) that ends in .stl, .obj, .ply, .glb or .gltf, up to 32 MiB including glTF buffer files in the same directory, and returns only measurements and mesh names; no network, file writes, rendering or repair; enabling it installs trimesh, pygltflib and numpy.

TakeshiTGALToolsv0.1.0Updated 5 days ago

About

Mesh Check reads one local STL, OBJ, PLY, GLB, or glTF file and returns whether it is closed, its volume, its bounds, and mesh, animation, and material counts. Use it before a 3D print or a game export. Disclosure — reads any local file path the agent passes (following symlinks) that ends in .stl, .obj, .ply, .glb or .gltf, up to 32 MiB including glTF buffer files in the same directory, and returns only measurements and mesh names; no network, file writes, rendering or repair; enabling it installs trimesh, pygltflib and numpy.

Mesh Check

Mesh Check reads one local STL, OBJ, PLY, GLB, or glTF file and returns whether that mesh is closed, the volume when the file holds one closed mesh, the bounding box, and the mesh, animation, and material counts. Use it before a 3D print and before a game export. A numeric check does not guarantee that the mesh looks right. The call is local. It does not render, generate, repair, or open a network connection.

What one call returns

mesh_check takes path, a local file path. The reply is one JSON object.

FieldWhat you get
oktrue when the file was measured. false when the check stops.
watertightWhether the one measured mesh is closed. null when the file holds several meshes.
volumeThe solid volume of that one closed mesh. null when the mesh is open or the file holds several meshes.
boundsThe box around the shape: min, max, and size. An STL file has no unit, so units is "file".
face_countHow many triangles the check counted.
vertex_countHow many positions the check counted.
stored_vertex_countHow many positions the file stored.
mesh_countHow many meshes the file records.
measured_mesh_countHow many meshes this check measured.
animation_countHow many animations the file records. STL, OBJ, and PLY report 0.
material_countHow many materials the file records.
scene_countHow many scenes a glTF or GLB file records. Other formats leave this null.
node_countHow many nodes a glTF or GLB file records. Other formats leave this null.

The tool opens the path you pass and follows a symlink on that path. It stops at 33554432 bytes. It asks for no approval, and it registers no skill and no cron job. hermes tools disable mesh-check --platform telegram hides the tool there.

Details

watertight is true or false when the file holds one measured mesh. A file with several meshes, or geometry this check does not measure, leaves it null and sets watertight_reason.

volume is a number only when that one mesh is closed, its winding is consistent, and the value stays finite and greater than zero after rounding to 9 decimal places. Any other case leaves volume null and sets volume_reason. A rounded value of 0 sets volume_reason to volume_below_precision. A surface that is open can still have a nonzero surface integral. That integral is not returned.

bounds has min, max, and size from the finite vertex coordinates. Each end is rounded to 9 decimal places. A nonzero value that those places would turn into 0 stays in scientific form. size is the difference of the published ends. That difference is kept, with no second pass through the 9-decimal rounding. When both ends would land on the same 9-decimal value and the vertices still span a nonzero extent, each end keeps its offset from that shared value in scientific form. size is still the difference of the published ends. Lengths are the numbers in the file.

face_count is the triangle count. A face with more than three corners is split into triangles from its first corner. vertex_count is the count of unique positions after coordinates that match exactly are joined. A gap stays open. stored_vertex_count is the count before that join.

mesh_count, animation_count, and material_count come from the file. A glTF or GLB file counts meshes, animations, and materials in the document. STL, OBJ, and PLY have no animation channel, so animation_count is 0 and animation_source is not_in_format. An OBJ file counts distinct usemtl names and does not open a .mtl file. A PLY file uses element material when that element is present.

One glTF or GLB mesh entry can store several primitives. Each primitive is measured as its own mesh. Two primitives in one mesh entry keep mesh_count at 1 and set measured_mesh_count to 2. watertight and volume stay null. watertight_reason and volume_reason are mesh_count_disagrees.

An ASCII STL with several solid sections counts several meshes, so the top-level volume stays null and each mesh keeps its own volume. A binary STL is one mesh, including when it holds several shells. That volume adds the shells. It is not the volume of their union. Shells that share the same vertex positions are welded first, and the closed test then sees the joined surface.

scene_count and node_count are filled for glTF and GLB. Other formats leave them null with source not_in_format.

Identical coordinates become one vertex. The join does not move a vertex to close a crack. Volume is omitted unless the file is one closed mesh with consistent winding and a volume that stays greater than zero after rounding to 9 decimal places.

A glTF buffer URI with a scheme, a .. segment, a symlink, or a path outside the opened file's directory is refused before the file is loaded. The byte cap counts a glTF buffer that stays inside that directory. Enable prepares trimesh and pygltflib in the shared Hermes environment. Numpy is installed with trimesh. pygltflib also brings dataclasses-json, which asks for marshmallow 3. Scipy, networkx, rtree, shapely, manifold3d, and httpx are not installed with those packages.

Anyone allowed on the gateway can call the tool on a path the Hermes process can open.

When the check stops

Each failure names a next step.

kindnext step
broken fileExport the mesh again as STL, OBJ, PLY, GLB, or glTF.
unsupported formatSave the mesh as STL, OBJ, PLY, GLB, or glTF and pass that file.
file over 33554432 bytesExport a smaller file. This check stops at 33554432 bytes.
empty meshExport a mesh that contains triangles.

A missing path, a directory, a pipe, a missing package, and coordinates that are not finite each name their own next step in next_step. A URI in path uses this next step: Pass a local file path. From a file URI, drop the scheme first. A glTF buffer URI that leaves the opened file's directory uses this next step: Export a single GLB and pass that local file.

Thirty seconds

hermes on PATH is Hermes 0.22.2. The scene follows symlinks and uses the python beside the real hermes file. This scene does not call a model. It calls handle_function_call in model_tools.py, which is the dispatcher hermes chat uses after a tool call. --yes-deps is the consent to prepare trimesh and pygltflib in that shared environment.

set -eu
SCENE="$(mktemp -d)"
export HERMES_HOME="$SCENE/hermes"
mkdir -p "$HERMES_HOME"
hermes plugins install --no-enable --yes-deps "file://$PWD"
hermes plugins enable mesh-check
cat > "$HERMES_HOME/config.yaml" << 'EOF'
_config_version: 50
plugins:
  enabled:
    - mesh-check
approvals:
  mode: off
EOF
HERMES_BIN="$(command -v hermes)"
while [ -L "$HERMES_BIN" ]; do
  _dest="$(readlink "$HERMES_BIN")"
  case "$_dest" in
    /*) HERMES_BIN="$_dest" ;;
    *) HERMES_BIN="$(dirname "$HERMES_BIN")/$_dest" ;;
  esac
done
PY="$(dirname "$HERMES_BIN")/python"
WORK="$SCENE/work"
mkdir -p "$WORK"
cd "$WORK"
"$PY" - "$WORK" << 'PY'
import json
import struct
import sys
from pathlib import Path

from hermes_cli.plugins import discover_plugins
from model_tools import handle_function_call

work = Path(sys.argv[1])
verts = [
    (0.0, 0.0, 0.0),
    (1.0, 0.0, 0.0),
    (1.0, 1.0, 0.0),
    (0.0, 1.0, 0.0),
    (0.0, 0.0, 1.0),
    (1.0, 0.0, 1.0),
    (1.0, 1.0, 1.0),
    (0.0, 1.0, 1.0),
]
faces = [
    (0, 3, 2),
    (0, 2, 1),
    (4, 5, 6),
    (4, 6, 7),
    (0, 1, 5),
    (0, 5, 4),
    (1, 2, 6),
    (1, 6, 5),
    (2, 3, 7),
    (2, 7, 6),
    (3, 0, 4),
    (3, 4, 7),
]
blob = bytearray(b"cube" + b"\0" * 76)
blob += struct.pack("<I", len(faces))
for a, b, c in faces:
    corners = (0.0, 0.0, 0.0) + verts[a] + verts[b] + verts[c]
    blob += struct.pack("<12fH", *corners, 0)
cube = work / "cube.stl"
cube.write_bytes(blob)

discover_plugins(force=True)
unchanged = handle_function_call(
    "terminal",
    {"command": "echo hello-unchanged"},
    skip_pre_tool_call_hook=True,
)
print("UNCHANGED")
print(unchanged)
checked = handle_function_call(
    "mesh_check",
    {"path": str(cube)},
    skip_pre_tool_call_hook=True,
)
print("CHECK")
print(checked)
body = json.loads(checked)
print(
    "FIELDS",
    json.dumps(
        {
            "ok": body.get("ok"),
            "watertight": body.get("watertight"),
            "volume": body.get("volume"),
            "face_count": body.get("face_count"),
            "vertex_count": body.get("vertex_count"),
        },
        sort_keys=True,
    ),
)
PY

The second scene clears HERMES_HOME and uses a fresh HOME. Hermes then uses $HOME/.hermes.

set -eu
SCENE="$(mktemp -d)"
export HOME="$SCENE/user"
mkdir -p "$HOME"
env -u HERMES_HOME HOME="$HOME" hermes plugins install --no-enable --yes-deps "file://$PWD"
env -u HERMES_HOME HOME="$HOME" hermes plugins enable mesh-check
HERMES_DIR="$HOME/.hermes"
cat > "$HERMES_DIR/config.yaml" << 'EOF'
_config_version: 50
plugins:
  enabled:
    - mesh-check
approvals:
  mode: off
EOF
HERMES_BIN="$(command -v hermes)"
while [ -L "$HERMES_BIN" ]; do
  _dest="$(readlink "$HERMES_BIN")"
  case "$_dest" in
    /*) HERMES_BIN="$_dest" ;;
    *) HERMES_BIN="$(dirname "$HERMES_BIN")/$_dest" ;;
  esac
done
PY="$(dirname "$HERMES_BIN")/python"
WORK="$SCENE/work"
mkdir -p "$WORK"
cd "$WORK"
env -u HERMES_HOME HOME="$HOME" "$PY" - "$WORK" << 'PY'
import json
import struct
import sys
from pathlib import Path

from hermes_cli.plugins import discover_plugins
from model_tools import handle_function_call

work = Path(sys.argv[1])
verts = [
    (0.0, 0.0, 0.0),
    (1.0, 0.0, 0.0),
    (1.0, 1.0, 0.0),
    (0.0, 1.0, 0.0),
    (0.0, 0.0, 1.0),
    (1.0, 0.0, 1.0),
    (1.0, 1.0, 1.0),
    (0.0, 1.0, 1.0),
]
faces = [
    (0, 3, 2),
    (0, 2, 1),
    (4, 5, 6),
    (4, 6, 7),
    (0, 1, 5),
    (0, 5, 4),
    (1, 2, 6),
    (1, 6, 5),
    (2, 3, 7),
    (2, 7, 6),
    (3, 0, 4),
    (3, 4, 7),
]
blob = bytearray(b"cube" + b"\0" * 76)
blob += struct.pack("<I", len(faces))
for a, b, c in faces:
    corners = (0.0, 0.0, 0.0) + verts[a] + verts[b] + verts[c]
    blob += struct.pack("<12fH", *corners, 0)
cube = work / "cube.stl"
cube.write_bytes(blob)

discover_plugins(force=True)
unchanged = handle_function_call(
    "terminal",
    {"command": "echo hello-unchanged"},
    skip_pre_tool_call_hook=True,
)
print("UNCHANGED")
print(unchanged)
checked = handle_function_call(
    "mesh_check",
    {"path": str(cube)},
    skip_pre_tool_call_hook=True,
)
print("CHECK")
print(checked)
body = json.loads(checked)
print(
    "FIELDS",
    json.dumps(
        {
            "ok": body.get("ok"),
            "watertight": body.get("watertight"),
            "volume": body.get("volume"),
            "face_count": body.get("face_count"),
            "vertex_count": body.get("vertex_count"),
        },
        sort_keys=True,
    ),
)
PY

Do not point HERMES_HOME at a profile you already use. hermes plugins disable mesh-check turns the tool off. hermes plugins remove mesh-check deletes the installed plugin directory. plugins.enabled becomes empty. The shared environment can keep numpy and trimesh. In the two installs for this tree, du -sk of the numpy 2.4.3 directory was 34220 KiB and 34108 KiB, and trimesh was 4660 KiB and 4664 KiB. That figure is the directory alone. Hermes can leave the toolset name in known_plugin_toolsets, a pyproject.toml under plugin-deps, the workspace pyproject.toml, uv.lock, and a config backup under backups/config. The installed plugin directory, including .git, is 364 KiB.

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

More by TakeshiTGAL

39 plugins by TakeshiTGAL in the catalog.

TakeshiTGALjp-subsidiesJapanese subsidy search and weekly watch, built on the jGrants public API. Disclosure — Searches api.jgrants-portal.go.jp with no API key and no daily request cap; each call waits at most 60 seconds and retries at most twice, and a result is a search match, not proof that every subsidy came back. The plugin has no user list of its own: anyone you allow on your Hermes gateway can call these tools and change this profile's watch, and the agent can set up a watch by itself. In a Chatwork room listed in CHATWORK_ROOMS, everyone can call them while CHATWORK_ALLOWED_USERS is unset. The tools are on for every platform, including gateways; turn them off per platform with hermes tools. While the plugin is enabled, its skill adds one line to the skills index of every session, including surfaces where the tools are turned off, and its pre_llm_call paragraph is added on those surfaces too. The /subsidies command is outside hermes tools; limit it with allow_admin_from or user_allowed_commands, or disable the plugin. The optional weekly watch is an unattended cron job that runs a script with no model call and is not a sandbox; delivering it to bot-chat instead runs one model turn on the fetched text. If delivery fails after the script runs, those subsidies are already marked seen and the text stays under cron/output/. Uninstall leaves the cron job, scripts/jp-subsidies-weekly-*.py and plugin-data/jp-subsidies/ until you run hermes cron remove and delete the files. The plugin does not store the name or ID of who asked. Not tested against a live gateway, with the Chatwork plugin loaded, or for result sets of several hundred rows. subsidies_detail compares a corporation's published industry, capital, employee count, and address with the call text as characters, returns a cap only when the call states one, and does not estimate an award. pre_tool_call blocks subsidies_search unless keyword is contained in industry text copied from a tool result, including a list of industry strings. A company name does not pass, including when the industry text is contained in the company name. When industry text was returned and the keyword is not that text, the block does not say the industry was missing. The block says the search was not run, eligibility is not_claimed, and no award was estimated. A company name contained in business_summary does not pass as an industry keyword. That holds when the name field is absent and the summary is トヨタ自動車は自動車を製造する。: トヨタ自動車 does not pass and 自動車 does. transform_tool_result remembers industry text and returns nothing, so the tool result is unchanged. pre_llm_call adds its paragraph only on a subsidy question (補助金, 助成金, jGrants, or 募集) or when subsidies_search, subsidies_detail, or subsidies_watch_setup was called in the previous turn, and adds nothing on other turns. A company name alone or an unrelated question does not add it. The paragraph says to call subsidies_search only with industry text copied from a tool result, that eligibility is not_claimed, and not to estimate an award or write 対象です.Communitytools1TakeshiTGALwyoming-voice-bridgeWyoming speech-to-text and text-to-speech for a Wyoming server you run (stt/tts provider wyoming), plus a wyoming_voice_status tool that lists the server's models and voices. Disclosure — Audio and text to speak go to the WYOMING_* host:port you set over cleartext, unauthenticated TCP (public addresses accepted). Once selected, the providers send speech in every session, including cron and webhooks. This build imports the installed package only when its file tree is the official wyoming 1.5.4 wheel, and a different tree sends nothing. This build lists no ffmpeg digest, so audio that is not already 16 kHz, 16-bit, mono WAV is not converted. wyoming_voice_status asks with one public pre_tool_call line. Choosing always stores one command_allowlist line for that same which and the same host:port list. A later call skips the question only when a person is present. cron, hermes -q, webhook, msgraph_webhook, and api_server do not send a describe, even after always. yolo and approvals off skip the prompt, and this plugin does not add a refusal for those modes. The plugin does not import Hermes approval, config, or write-guard modules. Hermes 0.21.4 does not list the skill. The v0.21.5 canary and Hermes 0.22.2 add one skill line to every session that loads the plugin, including a surface where the tools are turned off. The status tool is on for every surface, including the gateway, and a guest there can call it and approve it when a person can answer. Turn the wyoming_voice toolset off per surface with hermes tools.Communityvoice1TakeshiTGALauthor-feedEach watch run costs 0 tokens, and the unmanned run holds no tools. Read one public profile and watch one account, with profile_get, author_feed and author_watch. It reads public posts and profiles from the Bluesky social media network, which is built on the AT Protocol (atproto), without signing in. Disclosure — HTTPS GET only to public.api.bsky.app, no API key. Hermes starts the watch Python when the cron job fires. The tools are on for every surface, including gateways, and ask for no approval: anyone you allow on your gateway can call them. Turn a surface off with hermes tools. While the plugin is enabled, its skill adds one line to the skills index of every session, including surfaces where the tools are turned off. hermes author-feed schedule writes a script and creates one cron job that does not call a model. Each run costs 0 tokens and has no daily cap. Empty script output sends nothing. Delivered to local unless you pass --deliver, so no chat by default. Run hermes author-feed unschedule before removal. That removes the job and the script. A leftover job after the plugin is gone stops with hermes cron remove <id>. The scheduled script does not run under plugins.isolation: host, so that setting does not stop the watch. The author_watch tool still refuses a run that is not the saved cron job, including under plugins.isolation: host, and posts that notice on every run of the tool. The first run only records what is already there. One run reads at most the latest 3 pages and announces a new post by this account on them. When every row on those pages is new, with no saved post or mark, and the feed still offers another cursor, it also posts a possible-miss notice, at most once in 24 hours while that keeps happening. Replies, including the account's own thread continuations, are not announced. It relies on private Hermes parts, so an update can stop it. State stays in <HERMES_HOME>/plugin-data/author-feed after uninstall. Seen post URIs advance only on the saved cron job after a successful fetch. The script allows that when cron/executions.db shows that job running under the parent pid and cron/jobs.json names author-feed-watch.py. A direct run and another cron job exit 3 with no GET and no write. The author_watch tool allows that only for the saved job id. Delivery accepts origin, local, all, bot-chat, the Hermes 0.21.6 cron platform names, and public registry names that declare a cron delivery env var. A refused name can be set with hermes cron edit <id> --deliver. bot-chat places the watched account's post text in another model turn that has the profile's tools. hermes cron create cannot set a per-job tool list. A job made by 0.1.x keeps its model turn until the next schedule. On Hermes 0.21.4 and 0.21.5 this plugin does not load, and a leftover job keeps its model turn until hermes cron remove <id>. Running schedule again updates the interval and deliver target and switches an existing model job to the script.CommunitytoolsTakeshiTGALcsharp-game-editorGive it one feature for the Unity project open in your editor, and it builds the scripts, objects and scene in one plan, stops that plan when the compile reports an error CS line, and plays the scene when the compile is clean. Disclosure — Needs MCP for Unity pinned to v10.3.0, plus git and uv. Hermes starts mcpforunityserver==10.3.0 through uvx with telemetry and the update check off. Disk reads run at once. apply_plan asks once and puts back a file the plan did not name. A plan that deletes, runs editor code, can lose unsaved work or writes outside the project asks again, and that summary is sent only when every line fits the approval card; otherwise nothing is sent and confirm_risky_plan asks. unity_docs sends the query to docs.unity3d.com after Hermes asks. unity_generate can call paid providers you configured in MCP for Unity; that call was not part of the check. Tools are on by default on every surface, including the gateway. Only users the gateway admits can reach the tools, and this plugin keeps no user list of its own. Cron and a session with nobody to answer decline. Logs stay in <HERMES_HOME>/plugin-data/agent-plugin-csharp-game-editor-<hash>/logs. Stop with hermes plugins disable csharp-game-editor, or hermes tools for one surface. macOS only.Communitytools

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section