All plugins

us-filings

US Filings lists recent SEC EDGAR filings for a ticker or CIK and locates one by accession number. It sends one morning message when a watched company files. Disclosure — HTTPS only to data.sec.gov and www.sec.gov (US SEC), no API key, no proxy, no redirects; US_FILINGS_CONTACT is read with get_secret each call; add and remove use pre_tool_call, yolo and approvals off skip it if a person is present, and cron, hermes -q, webhook, or a separate process cannot add or remove even after always; hermes cron create --no-agent --script creates the job, empty stdout sends nothing, and the job, scripts/us-filings-watch.py, and plugin-data/us-filings/state.json stay after uninstall; tools are on every surface.

TakeshiTGALToolsv0.1.0Updated 5 days ago

About

US Filings lists recent SEC EDGAR filings for a ticker or CIK and locates one by accession number. It sends one morning message when a watched company files. Disclosure — HTTPS only to data.sec.gov and www.sec.gov (US SEC), no API key, no proxy, no redirects; US_FILINGS_CONTACT is read with get_secret each call; add and remove use pre_tool_call, yolo and approvals off skip it if a person is present, and cron, hermes -q, webhook, or a separate process cannot add or remove even after always; hermes cron create --no-agent --script creates the job, empty stdout sends nothing, and the job, scripts/us-filings-watch.py, and plugin-data/us-filings/state.json stay after uninstall; tools are on every surface.

US Filings

Say "Show recent filings for AAPL" and the reply lists the form, the filing date, the accession number, and the document location.
Ask for a document by its accession number and the reply gives the EDGAR index URL and the primary document URL.
Ask to watch AAPL each morning and one message is sent only when a new accession number appears. The first complete read sends nothing.

Install and first call

From this directory:

hermes plugins install "file://$PWD"
hermes plugins enable us-filings
hermes us-filings call us_filings_recent --json '{"ticker":"AAPL"}'

The first call needs no network when US_FILINGS_CONTACT is unset. The JSON has ok false, kind contact_unset, error_type contact_unset, and next_step. Copy next_step. It names the profile .env line and the SEC fair-access page.

Put your own name and email on one line in the active profile .env:

US_FILINGS_CONTACT=Your Name you@your-domain.example

The plugin sends that string as the User-Agent. It does not add its own name or email. The value is read again on every SEC call through agent.secret_scope.get_secret. It is not printed. The morning script binds the profile secret scope with build_profile_secret_scope and set_secret_scope, then the same get_secret read. An HTTP proxy in the environment is not used. Redirects are not followed. The plugin waits 0.2 seconds between its own SEC calls and stays under the SEC limit of 10 requests a second. There is no daily cap.

After the contact is set, the same command lists recent filings. Each row has the form, the filing date, the accession number, an index URL, and a primary document URL.

Details

US Filings sends one morning message when a watched US company has a new SEC filing. You can also list recent filings for a ticker or CIK, and locate a document by accession number. It does not read financial figures.

Linux and macOS are the listed platforms. Hermes 0.21.6 or newer is required. The cron mark is cron.execution_identity.current_cron_execution, and hermes cron create --no-agent is already in that line. These checks ran on Hermes 0.22.2.

The tools are on for every surface, including gateways. One surface turns off with hermes tools disable us_filings --platform telegram.

A pasted SEC URL on www.sec.gov or data.sec.gov is read as the CIK or the ticker inside it. A trailing # comment is dropped before the ticker or the accession number is read. A non-SEC URL is refused.

Tools

us_filings_recent takes ticker or cik, an optional limit from 1 to 40 (default 20), and an optional forms list. The recent window can be longer than limit. window_count is the number that was read. A shorter shown does not mean those rows are the whole window.

us_filings_locate takes accession and, unless a saved watch already has that accession, ticker or cik. The directory in the URL is the subject company CIK from the submissions file. The accession prefix is the filer CIK and can belong to an agent, so it is not used as the directory. An accession that is outside filings.recent is not called absent. The reply names the window count and the date span. Older pages listed under filings.files are not read.

us_filings_watch takes action add, remove, or list. Add requires hour from 0 through 23 and deliver. deliver is local, origin, or a platform target you choose. One job named us-filings serves every watched company, at 0 <hour> * * *. The prompt passed to cron is US Filings morning check. The script is us-filings-watch.py. At most 20 companies are stored. The default form list is every form, including Form 4 and 13F. Pass forms when you want a subset in the morning line. The seen set is still every accession in the recent window.

List is read only. Recent and locate are read only. They do not ask for approval and they do not mark filings seen.

Hooks

pre_tool_call returns the approve line for add and remove. Recent, locate, and list return no approval line. The conversation text stays as the user wrote it.

Approval

Add and remove return {"action":"approve","message":...} from pre_tool_call. The approval card command field shows the tool name us_filings_watch. The message contains the full hermes cron command when a cron command will run, plus plugin-data/us-filings/state.json. The handler runs those same cron arguments.

yolo and approvals.mode: off skip the prompt when a person is present. The hook still records the plan. A cron job, hermes -q, a webhook, and a separate plugin process cannot add or remove a company even after always. Answering always on add covers that same add plan only while a person is present. Remove builds a new rule key on every call, so always on remove does not cover the next remove.

If the approval message does not fit in one message, the hook blocks and nothing is saved.

Morning job

The first complete read of a company stores the accession numbers and prints no filing line. A later morning prints one block per new accession number: company, ticker, CIK, form, filing date, acceptance time when SEC sent one, accession number, index URL, and primary document URL. It does not say the filing arrived this morning. A repeated accession is not printed again when the document text changes. Dropped accession numbers leave the seen set and are not printed. The same set in a different order prints nothing.

Empty stdout sends nothing. Each run costs 0 tokens and holds no tools. There is no daily cap. A company that was not fully read is left unseen, and the script exits non-zero so cron can show the failure. Companies that were fully read can still update, and their new lines can be on stdout inside that failure.

The script stdout goes to the deliver value. local keeps it in the cron output on this machine. origin sends it to the chat that created the job when that chat is known. A platform target needs that platform connected on the Hermes gateway. With no gateway running, the job is stored and does not fire.

The job and scripts/us-filings-watch.py remain after hermes plugins remove or disable. Remove them with hermes cron remove <id>. When the profile is not default, add -p and the profile name. The state file remains at plugin-data/us-filings/state.json until you delete that directory.

The SEC fair-access page is https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data.

README from the reviewed commit 9ffdeef; it updates when the author re-pins.

More by TakeshiTGAL

39 plugins by TakeshiTGAL in the catalog.

TakeshiTGALjp-subsidiesJapanese subsidy search and weekly watch, built on the jGrants public API. Disclosure — Searches api.jgrants-portal.go.jp with no API key and no daily request cap; each call waits at most 60 seconds and retries at most twice, and a result is a search match, not proof that every subsidy came back. The plugin has no user list of its own: anyone you allow on your Hermes gateway can call these tools and change this profile's watch, and the agent can set up a watch by itself. In a Chatwork room listed in CHATWORK_ROOMS, everyone can call them while CHATWORK_ALLOWED_USERS is unset. The tools are on for every platform, including gateways; turn them off per platform with hermes tools. While the plugin is enabled, its skill adds one line to the skills index of every session, including surfaces where the tools are turned off, and its pre_llm_call paragraph is added on those surfaces too. The /subsidies command is outside hermes tools; limit it with allow_admin_from or user_allowed_commands, or disable the plugin. The optional weekly watch is an unattended cron job that runs a script with no model call and is not a sandbox; delivering it to bot-chat instead runs one model turn on the fetched text. If delivery fails after the script runs, those subsidies are already marked seen and the text stays under cron/output/. Uninstall leaves the cron job, scripts/jp-subsidies-weekly-*.py and plugin-data/jp-subsidies/ until you run hermes cron remove and delete the files. The plugin does not store the name or ID of who asked. Not tested against a live gateway, with the Chatwork plugin loaded, or for result sets of several hundred rows. subsidies_detail compares a corporation's published industry, capital, employee count, and address with the call text as characters, returns a cap only when the call states one, and does not estimate an award. pre_tool_call blocks subsidies_search unless keyword is contained in industry text copied from a tool result, including a list of industry strings. A company name does not pass, including when the industry text is contained in the company name. When industry text was returned and the keyword is not that text, the block does not say the industry was missing. The block says the search was not run, eligibility is not_claimed, and no award was estimated. A company name contained in business_summary does not pass as an industry keyword. That holds when the name field is absent and the summary is トヨタ自動車は自動車を製造する。: トヨタ自動車 does not pass and 自動車 does. transform_tool_result remembers industry text and returns nothing, so the tool result is unchanged. pre_llm_call adds its paragraph only on a subsidy question (補助金, 助成金, jGrants, or 募集) or when subsidies_search, subsidies_detail, or subsidies_watch_setup was called in the previous turn, and adds nothing on other turns. A company name alone or an unrelated question does not add it. The paragraph says to call subsidies_search only with industry text copied from a tool result, that eligibility is not_claimed, and not to estimate an award or write 対象です.Communitytools1TakeshiTGALwyoming-voice-bridgeWyoming speech-to-text and text-to-speech for a Wyoming server you run (stt/tts provider wyoming), plus a wyoming_voice_status tool that lists the server's models and voices. Disclosure — Audio and text to speak go to the WYOMING_* host:port you set over cleartext, unauthenticated TCP (public addresses accepted). Once selected, the providers send speech in every session, including cron and webhooks. This build imports the installed package only when its file tree is the official wyoming 1.5.4 wheel, and a different tree sends nothing. This build lists no ffmpeg digest, so audio that is not already 16 kHz, 16-bit, mono WAV is not converted. wyoming_voice_status asks with one public pre_tool_call line. Choosing always stores one command_allowlist line for that same which and the same host:port list. A later call skips the question only when a person is present. cron, hermes -q, webhook, msgraph_webhook, and api_server do not send a describe, even after always. yolo and approvals off skip the prompt, and this plugin does not add a refusal for those modes. The plugin does not import Hermes approval, config, or write-guard modules. Hermes 0.21.4 does not list the skill. The v0.21.5 canary and Hermes 0.22.2 add one skill line to every session that loads the plugin, including a surface where the tools are turned off. The status tool is on for every surface, including the gateway, and a guest there can call it and approve it when a person can answer. Turn the wyoming_voice toolset off per surface with hermes tools.Communityvoice1TakeshiTGALauthor-feedEach watch run costs 0 tokens, and the unmanned run holds no tools. Read one public profile and watch one account, with profile_get, author_feed and author_watch. It reads public posts and profiles from the Bluesky social media network, which is built on the AT Protocol (atproto), without signing in. Disclosure — HTTPS GET only to public.api.bsky.app, no API key. Hermes starts the watch Python when the cron job fires. The tools are on for every surface, including gateways, and ask for no approval: anyone you allow on your gateway can call them. Turn a surface off with hermes tools. While the plugin is enabled, its skill adds one line to the skills index of every session, including surfaces where the tools are turned off. hermes author-feed schedule writes a script and creates one cron job that does not call a model. Each run costs 0 tokens and has no daily cap. Empty script output sends nothing. Delivered to local unless you pass --deliver, so no chat by default. Run hermes author-feed unschedule before removal. That removes the job and the script. A leftover job after the plugin is gone stops with hermes cron remove <id>. The scheduled script does not run under plugins.isolation: host, so that setting does not stop the watch. The author_watch tool still refuses a run that is not the saved cron job, including under plugins.isolation: host, and posts that notice on every run of the tool. The first run only records what is already there. One run reads at most the latest 3 pages and announces a new post by this account on them. When every row on those pages is new, with no saved post or mark, and the feed still offers another cursor, it also posts a possible-miss notice, at most once in 24 hours while that keeps happening. Replies, including the account's own thread continuations, are not announced. It relies on private Hermes parts, so an update can stop it. State stays in <HERMES_HOME>/plugin-data/author-feed after uninstall. Seen post URIs advance only on the saved cron job after a successful fetch. The script allows that when cron/executions.db shows that job running under the parent pid and cron/jobs.json names author-feed-watch.py. A direct run and another cron job exit 3 with no GET and no write. The author_watch tool allows that only for the saved job id. Delivery accepts origin, local, all, bot-chat, the Hermes 0.21.6 cron platform names, and public registry names that declare a cron delivery env var. A refused name can be set with hermes cron edit <id> --deliver. bot-chat places the watched account's post text in another model turn that has the profile's tools. hermes cron create cannot set a per-job tool list. A job made by 0.1.x keeps its model turn until the next schedule. On Hermes 0.21.4 and 0.21.5 this plugin does not load, and a leftover job keeps its model turn until hermes cron remove <id>. Running schedule again updates the interval and deliver target and switches an existing model job to the script.CommunitytoolsTakeshiTGALcsharp-game-editorGive it one feature for the Unity project open in your editor, and it builds the scripts, objects and scene in one plan, stops that plan when the compile reports an error CS line, and plays the scene when the compile is clean. Disclosure — Needs MCP for Unity pinned to v10.3.0, plus git and uv. Hermes starts mcpforunityserver==10.3.0 through uvx with telemetry and the update check off. Disk reads run at once. apply_plan asks once and puts back a file the plan did not name. A plan that deletes, runs editor code, can lose unsaved work or writes outside the project asks again, and that summary is sent only when every line fits the approval card; otherwise nothing is sent and confirm_risky_plan asks. unity_docs sends the query to docs.unity3d.com after Hermes asks. unity_generate can call paid providers you configured in MCP for Unity; that call was not part of the check. Tools are on by default on every surface, including the gateway. Only users the gateway admits can reach the tools, and this plugin keeps no user list of its own. Cron and a session with nobody to answer decline. Logs stay in <HERMES_HOME>/plugin-data/agent-plugin-csharp-game-editor-<hash>/logs. Stop with hermes plugins disable csharp-game-editor, or hermes tools for one surface. macOS only.Communitytools

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section