hermes-admin/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

chore(plugin-catalog): fleet-policy disclosure at merge

Browse Source
This commit is contained in:
Teknium
2026-10-04 22:53:36 -07:00
parent 843a185edf
commit 1cdbe9b4f3
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
plugin-catalog/fleet-policy.yaml
View File

@@ -2,7 +2,7 @@ name: fleet-policy
repo: https://github.com/Julientalbot/hermes-fleet-policy
sha: 7d36874a5a625fc2a0c24ee280e34872e5259800
subdir: fleet_policy
description: "For administrators who pin settings through the managed scope: records what each agent role really sends to the provider (model, reasoning effort, service tier, plus the tier the provider says it served) next to the managed-scope state and the effective config (`hermes fleet-policy status --json`); measures cron cost per job — runs, empty runs, $/day, gate present (`crons --cost`); and `watch`, a generic wake gate for cron scripts that replays one read tool on an MCP server and wakes the agent only when new item ids appear (stock `wakeAgent` gate, no LLM call otherwise). Ships two skills (managed-scope admin, recurring tasks). Disclosure — observes request metadata through the public `pre_api_request` / `pre_auxiliary_call` hooks and a pass-through `llm_execution` middleware, never message content or credentials, stored in $HERMES_HOME/fleet-policy/; reads cron/executions.db and state.db read-only; `watch` calls only the MCP endpoint written in its config (or the one an admin pins via `watch_server_url`) and stores seen ids in its state file; no other network access, no telemetry."
description: "For administrators who pin settings through the managed scope: records what each agent role really sends to the provider (model, reasoning effort, service tier, plus the tier the provider says it served) next to the managed-scope state and the effective config (`hermes fleet-policy status --json`); measures cron cost per job — runs, empty runs, $/day, gate present (`crons --cost`); and `watch`, a generic wake gate for cron scripts that replays one read tool on an MCP server and wakes the agent only when new item ids appear (stock `wakeAgent` gate, no LLM call otherwise). Ships two skills (managed-scope admin, recurring tasks). Disclosure — records only model, reasoning effort and service tier per role (no message content, headers or keys) via the pre_api_request and pre_auxiliary_call hooks and a pass-through llm_execution middleware, stored in $HERMES_HOME/fleet-policy/observed.json; crons --cost opens cron/executions.db and state.db read-only and checks each cron run's final reply locally for silence; watch is an operator CLI command that calls one MCP tool at the config's server_url (or the admin-pinned watch_server_url) with config headers in which ${VAR} env values are expanded, follows redirects, and writes seen ids to a state file at the config-chosen path; the recurring-tasks skill has the agent write watch configs under $HERMES_HOME/watches, a script under $HERMES_HOME/scripts and a cron job; no other network access, no telemetry."
maintainer: Julientalbot
tier: community
category: automation