All plugins

mister-ideas

GitHub profile2 plugins in the catalog6

Plugins by mister-ideas

2 plugins by mister-ideas in the catalog, most-starred first.

mister-ideasgit-reviewGit review pane for Hermes Desktop: every changed file of the agent's last turn, uncommitted, staged or unstaged work, the branch since it left the default branch, or any selection of commits, in one scroll, unified or split, with syntax colours; cites changed lines into the composer as @line: references; and stages, unstages, discards, commits, pushes and opens pull requests from the pane. Disclosure — reads run git subprocesses (rev-parse, status, diff, log, show, cat-file, ls-files, for-each-ref, branch, remote, rev-list, merge-base, symbolic-ref, hash-object) with timeouts and output caps, external diff and textconv drivers disabled. Writes run only when the user clicks: git add, restore, reset, rm, commit and push, on paths validated inside the repository; discard asks first in Desktop's confirmation dialog and deletes only the untracked files it names. By default hooks are skipped and any write that would run a program named by the repository's own config (filter drivers, signing, SSH or credential commands) is refused; the run_repo_programs setting allows them, and the read_only setting hides and refuses every write. Network use: push to the branch's own name on its remote, and the user's own gh or glab CLI for the PR/MR badge and for Create pull request; the plugin itself makes no network requests. Generate commit message sends what the commit will contain and recent commit subjects to the focused chat's model through Hermes's commit_message one-shot template, only when clicked. It reads files and history inside authorized repositories only (the focused workspace, configured repos/roots and the latest agent selection), this profile's config.yaml, and the cwd column of the sessions table in state.db (read-only); it writes $HERMES_HOME/plugin-data/git-review/select.sqlite3 (agent selection requests), $HERMES_HOME/plugin-data/git-review/turn-snapshots/ (Last agent turn snapshots: the working tree's tracked and non-ignored untracked files as git objects, written with git add -A and write-tree against a throwaway index and an object store in that directory, never the repository's; newest 16 kept, three days max), Desktop plugin storage (display settings, turn baselines) and, through the actions above, the user's repository. While the pane is open it polls the local backend every 3 s (agent selections) and 5 s (live diffs); the status-bar count and the commit box's branch state refresh every 15 s; no background processes, credentials or telemetry.CommunityDesktop app3mister-ideasusage-guardKeeps an agent inside its subscription allowance: refuses a provider dispatch once a subscription usage window is exhausted, so an account that allows paid extra usage stops at the wall instead of spending overage. Reads the usage Hermes already displays, holds no credentials, and never touches account or billing settings. Disclosure — refuses main-loop provider calls (including MoA turns) for the providers in provider_keys (Anthropic and OpenAI Codex by default) when a subscription usage window reaches threshold_percent (a lone Anthropic reading of exactly 100% with extra usage off is treated as possibly 1%, because Hermes's Anthropic parser scales any utilization <= 1 by 100 until hermes-agent#139916, and passes; a 100% that follows a higher reading in the same window, or any 100% while extra usage is on, refuses), and by default (fail_open: false) also refuses when usage data is missing, stale, unreadable, or the guard's own config is malformed; usage is read through Hermes's own account-usage fetcher (no credentials held, at most one read per source every 180 seconds by default) and cached in $HERMES_HOME/plugin-data/usage-guard/usage.json; a pre_llm_call hook adds a short usage note to the next turn's context at 80% and 90% used by default, and an opt-in (off by default) llm_request middleware lowers an existing output-token budget near the usage limit; both read only the cache, never the network; a /usage-guard slash command and a Hermes Desktop status-bar chip (polling a read-only GET /api/plugins/usage-guard/status route every 60 s and after each turn) report the guard's decision from the same cache, never making a usage request; a refusal is an explanatory assistant message by default (refusal_mode: notice); with the opt-in refusal_mode: empty it is an empty reply instead, so Hermes's empty-response recovery retries (each retry refused again, never dispatched) and then switches to the profile's fallback_providers, which the guard gates only when they are listed in provider_keys; auxiliary calls (compression, vision, titles, MoA advisors) are not gated. Borrowing is off by default: when hydrate_from_paths names files, the guard may read those JSON snapshots instead of reading the endpoint, validating every window and never writing them into its own cache.Communityautomation3