5d59366010
Every entry is pinned to the commit reviewed on 2026-09-15 and passed, at that commit: `hermes plugins validate` (declared tools/hooks/middleware match registrations, no built-in tool collisions) in both the main venv and a bare `pip install -e .` venv, `tools.plugin_guard.scan_plugin` with a non-dangerous verdict, a self-updater grep over every .js file, and a vendor-credential-store write grep over every .py file. Capabilities and requires_env are copied from each plugin.yaml; category was assigned by hand.
17 lines
672 B
YAML
17 lines
672 B
YAML
name: recency-anchor
|
|
repo: https://github.com/etkecc/hermes-recency-anchor
|
|
sha: 24d1906a285fdfe37ecaf6253da8712db28f5a7b
|
|
description: Your system prompt is message zero and the user's question is message N. On models that weight
|
|
recency hard, that is not a fair fight, and the instruction you care about most quietly loses to whatever
|
|
was just asked. This plugin restates it at the end of every user turn instead. Append-only, API cop
|
|
maintainer: etkecc
|
|
tier: community
|
|
category: general
|
|
docs_url: https://github.com/etkecc/hermes-recency-anchor#readme
|
|
capabilities:
|
|
provides_tools: []
|
|
provides_hooks:
|
|
- pre_llm_call
|
|
provides_middleware: []
|
|
requires_env: []
|