hermes-finance.yaml 3.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. name: hermes-finance
  2. title: Hermes Finance
  3. repo: https://github.com/apelabs-dev/hermes-finance
  4. sha: "92a84ac59df2d98cb138d0c224eca6f7a42f2e36"
  5. subdir: hermes_plugin
  6. version: "0.2.6"
  7. description: "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."
  8. maintainer: "arspesk"
  9. tier: community
  10. category: tools
  11. docs_url: https://github.com/apelabs-dev/hermes-finance/blob/92a84ac59df2d98cb138d0c224eca6f7a42f2e36/README.md#install-as-a-hermes-plugin
  12. image: https://raw.githubusercontent.com/apelabs-dev/hermes-finance/92a84ac59df2d98cb138d0c224eca6f7a42f2e36/docs/assets/catalog-banner.jpg
  13. screenshots:
  14. - https://raw.githubusercontent.com/apelabs-dev/hermes-finance/92a84ac59df2d98cb138d0c224eca6f7a42f2e36/docs/assets/screenshots/showcase.jpg
  15. readme: false
  16. platforms: []
  17. known_issues:
  18. - "Needs a trusted hermes-finance app checkout prepared with Python 3.12 and `uv sync`; set HERMES_FINANCE_APP_DIR to it."
  19. - "`hermes plugins validate` warns (rule 9) about imports of gateway.session_context, tools.approval, cron.jobs and cron.scheduler: they keep approvals blocked in unattended runs and drive the opt-in report jobs; no core function is patched."
  20. capabilities:
  21. provides_tools:
  22. - finance_spend
  23. - finance_budget_status
  24. - finance_transactions
  25. - finance_networth
  26. - finance_bills
  27. - finance_loans
  28. - finance_holdings
  29. - finance_cashflow
  30. - finance_status
  31. - finance_goals
  32. - finance_rules
  33. - finance_sync
  34. - finance_set_category
  35. - finance_add_rule
  36. - finance_set_cap
  37. - finance_track_bill
  38. provides_hooks:
  39. - pre_tool_call
  40. provides_middleware: []
  41. requires_env: []