All plugins

arspesk

GitHub profile2 plugins in the catalog129

Plugins by arspesk

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

arspeskhermes-financePersonal-finance tools over your own local hermes-finance database: spending, budgets, transactions, net worth, bills, loans, investments, cash flow, goals and categorization rules (read-only), a bank sync on request, and four writes (file a transaction, add a rule, set a budget cap, track a bill) that each wait for your approval and are blocked under cron and other unattended runs. Needs a separate trusted app checkout prepared with Python 3.12 and uv sync, set as HERMES_FINANCE_APP_DIR. Disclosure — reads open the separate hermes-finance app's SQLite database outside the plugin directory, and the plugin imports that app checkout's code into the Hermes process, so it runs whatever that checkout contains, not the catalog pin. finance_sync runs the app's sync, which calls Plaid with your optional Plaid keys and fetches security logos from financialmodelingprep.com (ticker symbols leave the machine). hermes finance completion, started by the app's Ask panel, sends that conversation and your finance results to your profile's own model. The opt-in report jobs (hermes finance crons plan/apply) write profile-owned entry scripts and run the app on a schedule. They call Plaid and, with a live read-only key, Alpaca (GET-only); they look up car and home values through NHTSA, Wikimedia/OpenStreetMap and, only if you switch them on, Carfax (in the local Chrome at 127.0.0.1:9222) and Redfin. The daily job's agent applies transaction categorizations through the app's own CLI without a per-change approval card. The four approval-gated writes stay blocked in cron. Nothing moves money or places trades. The optional Plaid and Alpaca keys are read through Hermes's secret scope only; the plugin opens no key file. Installing starts no server, sync or job. No telemetry, no update check, no Python dependencies in Hermes.Communitytools98arspeskmock-reviewReview boards for UI mockups and plans. The agent builds a board from a decisions.json file and your prototype pages; you open it on desktop or phone, mark each decision approve, change or skip, pin comments on the mocks and press Send, and your agent wakes up with the feedback as a markdown digest. Plan boards add question cards and one footer button, Build, which stays locked until nothing is open and then wakes the agent with the approved plan; mocks carry working controls by default (interactive_elements). A design profile bound to a project is enforced: a round with off-profile colours or fonts is refused unless --off-brand gives a reason. 2.0 adds people: there are no passwords; the board server has accounts, single-use invites (hermes mockreview invite), per-review roles (viewer, commenter, reviewer) and one share link per review whose guests never wake Hermes. Pins are threads with replies, resolve and @Hermes mentions, and a round exports as PNG, PDF, HTML or Markdown. here.now hosting is removed; hermes mockreview migrate converts old here.now reviews to local or tailnet. 2.1 makes @Hermes work: an owner's or reviewer's @Hermes comment wakes Hermes, which replies in the thread, resolves it, or patches the anchored block in place when the comment asks for it (three new tools: mock_review_list_comments, mock_review_reply, mock_review_resolve); a guest, an agent token or a wake-off board never wakes anyone. Hermes Desktop gets a Mocks tab that lists reviews, shows a round read-only and deletes; commenting stays in the browser. Boards open in a flatter inline layout by default (layout: cards keeps the 2.0 look). 2.2 shows live which pins Hermes is working on (a pulsing red dot on the pin, a working chip on the block and a count in the header). 2.3 keeps resolved pins on the board (hide_resolved_pins hides them) and wakes the chat a board was made in on every messaging platform Hermes hosts, Hermes Desktop chats included; setup creates the wake and notice routes for every configured messaging platform. Nine mock_review tools, the hermes mockreview CLI and slash command, a bundled usage skill, and a stdio MCP server (bin/mockreview mcp) that serves the six board tools to Claude Code, Codex or OpenCode without Hermes, plus three comment tools when given a personal access token; that server starts only when you add it to such a client, and its boards do not wake an agent unless you pass --wake. Plain http(s) links in mocks stay clickable and open in a new tab; every other link scheme is stripped. Disclosure — when autostart is on (off until hermes mockreview setup), a board web server (127.0.0.1:8790 by default) and one worker thread run inside the gateway process; setting host to 0.0.0.0 shows every device on your network the sign-in page, where people join with an invite or a share link. With Hermes Desktop, the Mocks tab's backend is a plugin route (/api/plugins/mock-review/) served by the Hermes dashboard process behind the dashboard's session token; it only lists, renders and deletes reviews. Outbound calls: signed POSTs to the local Hermes webhook (localhost:8644, or the receiver you name in MOCKREVIEW_WEBHOOK_URL for the MCP server): the wake-up on Send, Build or an @Hermes comment, an instant acknowledgement, and a later stall notice that carries the review title and counts, never your notes; and, only when you set cloudflare_team and cloudflare_audience for Cloudflare Access sign-in, a GET of that team's signing keys at https://<team>.cloudflareaccess.com/cdn-cgi/access/certs. A board made in a Hermes Desktop chat is woken differently: the board server inside the gateway queues the wake prompt into that chat's own session through Hermes's plugin inject_message API, which Hermes allows only with plugins.entries.mock-review.allow_gateway_injection: true. Setup asks for that consent and sets it (with hermes config set) only on an explicit yes at a terminal, never under --yes. That turn runs with the chat's own tools, so a Desktop board is refused unless Send is gated (loopback, no public URL, no Funnel mapping, not a public board). Secrets: only MOCKREVIEW_WEBHOOK_SECRET, read through Hermes's secret scope or from the process environment when the stdio MCP server runs without Hermes; setup generates it; no credential file is read. Runs git -C <project> rev-parse --show-toplevel --git-common-dir (read only) to match a project to its bound design profile; runs tailscale status --json, tailscale serve status --json and tailscale funnel status --json (read only; on macOS the Tailscale app's own binary if the symlink crashes), and, only when you run hermes mockreview public on|off, tailscale funnel --bg --yes --https=<port> http://127.0.0.1:<board port> or tailscale funnel --https=<port> off to publish the board on a public Funnel URL behind sign-in; from setup it runs the hermes subcommands --version, gateway status, config get/set/unset, webhook subscribe, webhook remove (only for a stale self-delivering route, after you confirm) and plugins validate. The opt-in wake_toolsets setting lets the session woken by Send use the toolsets you list (for example terminal and file), so board feedback reaches those tools; setup refuses it while the server listens beyond loopback and only prints the toolsets line for you to add to the wake route by hand (re-add it after every setup run). Reviews, accounts and comments are stored under $HERMES_HOME/workspace/mock-reviews. No telemetry, no update check. One Python dependency, itsdangerous; the optional crypto extra adds PyJWT for Cloudflare Access sign-in.Communitytools31