Plugins by Ilyassbm
2 plugins by Ilyassbm in the catalog, most-starred first.
Ilyassbmhermes-templatesShare a whole Hermes agent as one .htemplate bundle and install it from a single HTTPS link: identity (SOUL.md), config with accounts and endpoints stripped, skills, routines, MCP server definitions, memories only when the author opts in, and plugin ids. A recipe, not a clone — credentials, sessions, conversation history, logs, caches and workspace never travel. Publish puts the bundle in a GitHub repository and returns one permanent link (re-publishing updates the same URL); Install previews a link, a path or a dropped file and shows the template itself before anything is written (SOUL.md, each skill, every routine's schedule and prompt, every MCP command, risky settings such as hooks with their values). Install enforces what the packer promises on any bundle: config sanitized again (approval and consent policy — command_allowlist, hooks_auto_accept, approvals, security — is always removed and the preview shows what was removed), routines imported paused through Hermes' cron API, MCP servers set enabled: false; plugins already installed here are enabled unless --no-enable-plugins. Reinstalling the same link offers "Update v1.0.0 → v1.1.0" and keeps memories, sessions and .env. Disclosure — reads the selected profile under HERMES_HOME (config.yaml, SOUL.md, skills/, cron/jobs.json, mcp.json, memories/ when opted in) and writes a new profile directory plus its own bundles under plugin-data/; the page may read a bundle only from HERMES_HOME or the home directory, the CLI has no such limit. Network: one HTTPS GET to a URL the user pastes (HTTPS and public hosts only on the page; http, LAN and local accepted in the CLI; every redirect re-checked, 20 MB cap) and, only when the user presses Publish, the GitHub REST API to upload the bundle and download it back to prove the link before it is shown; republishing writes the file at the same public URL. Installs drop approval and consent policy (command_allowlist, hooks_auto_accept, approvals, security), import routines paused and turn MCP servers off; plugins already installed here are enabled unless --no-enable-plugins. Credentials: the optional GITHUB_TOKEN is read with agent.secret_scope under the named profile, never stored in a bundle, logged or returned. No shell, no telemetry, no self-updater.CommunityDesktop appIlyassbmhermes-uiA bespoke chat workspace for Hermes Desktop and the Webapp: it takes over the app's home route and replaces it with a three-column page — a rail of bots (one row per profile, each with its own conversations), the conversation itself with folded reasoning and one working line that says what the bot is doing (tool calls are not listed; a call waiting for permission still shows its card), and a right panel for files, previews and session detail. Bots can answer with a structured block that the thread draws as rich components (status cards, tables, checklists, approval prompts) instead of prose, its questions answered in the thread with buttons, a multi-select and free text; links open in the OS browser; messages written while the bot works wait in a queue under the composer and go in order, slash commands, per-bot models and a settings page come with it (a model switch is sent to config.set without the confirmation flag; when the gateway asks to confirm a costly or data-policy-sensitive switch, its own message is shown in a dialog and the flag is sent only after the user clicks Switch), and media blocks render images, audio and video inline. Disclosure — takes over the Desktop/Webapp home route by default: opening home or a session from the native sidebar redirects into Hermes UI (a palette command turns this off). Its side panel previews files that replies name (MEDIA: lines, attached-image paths) by reading them through the plugin's own backend routes, which accept any path under the profile home or the user's home directory except core-refused and credential files (.env*, auth.json, config.yaml, credentials, webhook_subscriptions.json, private keys, .ssh/.aws/.gnupg, secrets, mcp-tokens and pairing folders); those local previews stay on the device. Web images a reply links to (markdown images, MEDIA: web addresses) are loaded by the app straight from their host, with no referrer. The bots rail reads each profile's state.db read-only. Changing a bot's look (shape, eyes, colour) writes ui_meta['hermes-ui'] in that profile's profile.yaml through Hermes' own profiles.configure. No telemetry.CommunityDesktop app
GitHub profile