All plugins

hermes-finance

Personal-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.

arspesk5Toolsv0.2.6Updated 5 days ago

About

Personal-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.

This plugin has no README in the catalog yet.

More by arspesk

2 plugins by arspesk in the catalog.

arspeskmock-reviewReview boards for UI mockups. 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. Four mock_review tools, the `hermes mockreview` CLI and slash command, and a bundled usage skill. Boards are served from your computer (loopback by default, or your tailnet) or published on here.now, behind a random per-review password by default (`herenow_password` setting, `--no-password` per review, `hermes mockreview password <id> on|off` on a live board). 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 exposes every review to your network with no login. Outbound calls: a signed POST to the local Hermes webhook (localhost:8644) on Send, and, only for reviews hosted on here.now, https://here.now/api/v1 with your HERENOW_API_KEY (publish, Site Data reads, a metadata PATCH that sets or removes the board password, delete on close). Secrets are read through Hermes's secret scope only. Runs `bash publish.sh` from the official here-now skill (key in the child environment), and for a password-protected here.now prototype launches your installed Chrome, Chromium or Edge headless (throwaway profile, credential-named variables removed from its environment, `--no-sandbox` only when run as root) to load the board behind its password before the link is shared; runs `tailscale status --json` and `tailscale serve status --json` (read only; on macOS the Tailscale app's own binary if the symlink crashes) for tailnet hosting, and from `setup` 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 any waking board is ungated and only prints the `toolsets` line for you to add to the wake route by hand (re-add it after every setup run). Reviews are stored under $HERMES_HOME/workspace/mock-reviews. No telemetry, no update check, no Python dependencies.Communitytools23