All plugins

manners-meter

How polite are you to your agent? Counts please, thank you, bitte, danke, por favor, merci and friends in the messages you typed (code blocks, quotes and injected system blocks skipped; cron, subagent, kanban, batch, webhook and tool sessions ignored), estimates the tokens your politeness cost (typed and re-sent with later calls of the same chat, an upper bound, not a bill), keeps a swear jar with a price per coin and gives a silly rank. /manners on every surface and hermes manners in the terminal, plus a share card (self-contained HTML, 1080x1920, no external assets). Disclosure: no network calls, no model calls, standard library only. Reads state.db of the active profile read only (mode=ro). Writes only the share card, by default to HERMES_HOME/plugin-data/manners-meter/manners-card.html. A pre_llm_call hook (jar_reactions, on by default) checks your new message for swear words; when it finds one it adds a short note with the matched word and the jar count to that user message (never to the system prompt) so the agent may answer with one dry line; jar_reactions: false turns it off. Session titles and message texts never appear in the output. No credentials, no shell commands, no cron jobs, no background processes, no telemetry.

MadeByBrain1Generalv1.0.0Updated 5 days ago

About

How polite are you to your agent? Counts please, thank you, bitte, danke, por favor, merci and friends in the messages you typed (code blocks, quotes and injected system blocks skipped; cron, subagent, kanban, batch, webhook and tool sessions ignored), estimates the tokens your politeness cost (typed and re-sent with later calls of the same chat, an upper bound, not a bill), keeps a swear jar with a price per coin and gives a silly rank. /manners on every surface and hermes manners in the terminal, plus a share card (self-contained HTML, 1080x1920, no external assets). Disclosure: no network calls, no model calls, standard library only. Reads state.db of the active profile read only (mode=ro). Writes only the share card, by default to HERMES_HOME/plugin-data/manners-meter/manners-card.html. A pre_llm_call hook (jar_reactions, on by default) checks your new message for swear words; when it finds one it adds a short note with the matched word and the jar count to that user message (never to the system prompt) so the agent may answer with one dry line; jar_reactions: false turns it off. Session titles and message texts never appear in the output. No credentials, no shell commands, no cron jobs, no background processes, no telemetry.

manners-meter: how polite are you to your agent?

manners-meter: politeness count, token cost and swear jar

Do you say "please" and "thank you" to your agent? manners-meter counts it. It reads the messages you typed in your own Hermes history and shows:

  • Politeness: how often you said please, thanks, thank you, sorry, bitte, danke, vielen dank, por favor, gracias, merci and a few more.
  • What it cost: an estimate of the tokens you typed for it, and how many tokens were re-sent with every later model call of the same chat.
  • The swear jar: every swear word you aimed at your agent is a coin in the jar. You set the price per coin.
  • Your rank: from "Cold Commander" to "Butler of Butlers", plus "Saint" to "Sailor" for the jar.
  • A share card: one HTML file in story format (1080 x 1920) to screenshot and post.

Optional and on by default: when one of your messages contains a swear word, the agent gets a short note with the new jar count and may answer with one dry line. Live example (Claude Haiku 4.5):

You: Damn, this shit keeps breaking. One sentence please.
Agent: Coin in the jar. What's breaking?

Read only, no model calls, no network. Standard library only.

Who it is for

  • Anyone who wondered whether "please" costs money. It is a running joke that politeness to chatbots costs real compute. This puts a number on your own share.
  • People who like to post their stats. The share card is built for stories and feeds, and it says that nothing was uploaded.
  • Teams and trainers, as a starting point. It is a light way to show what lands in the context of a model. It is not an analytics tool: counts are word matches, token figures are estimates.

Beyond this plugin

manners-meter is free and stays free. Real usage analytics for a company need its own data, so they are not a public plugin:

  • dashboards across all users and profiles of a company instance, with roles;
  • cost reports from the provider bills instead of estimates;
  • usage reviews that show where a team loses time or tokens.

MadeByBrain, the maintainer of this plugin, plans and builds such Hermes setups for businesses.

Install

hermes plugins install MadeByBrain/hermes-extensions/plugins/manners-meter --enable

Pin a release with --ref <40 character commit SHA> (tags are not accepted by --ref).

Use it

In any chat (CLI, TUI, Desktop, Telegram and the other gateways):

/manners           all time
/manners 30        last 30 days
/manners chat      this chat only
/manners card      write the share card and show its path
/manners json      raw numbers

In the terminal:

hermes manners
hermes manners --days 30
hermes manners --json
hermes manners --card              # default path under plugin-data/manners-meter/
hermes manners --card ~/card.html

Example output:

Manners meter (all time)
7,629 messages from you in 794 chats
You were polite 1,291x: "bitte" 834x, "danke" 218x, "please" 129x, "vielen dank" 43x, "thank you" 25x
Tokens you typed for it: 2,653
Re-sent with every later model call: about 510k (mostly from cache, at most $1.53 uncached at $3.00 per million)
Your agent answered "you're welcome": 2x
Swear jar: 11 coins = $11.00. Top word: mist
Rank: Polite Professional / Mostly Clean
Counted locally from state.db. Nothing left your machine.

The share card is plain HTML without external fonts, scripts or images. Open it in a browser and take a screenshot, or render it headless, for example with Chrome: chrome --headless --window-size=1080,1920 --screenshot=card.png card.html.

How it counts

  • Only what you typed. Code blocks, quoted lines (> ...) and injected system blocks are skipped. Sessions from cron, subagent, kanban, batch, webhook and tool are ignored, because a machine wrote those messages.
  • Word matches. Case insensitive, on word boundaries, so "pleased" or "mistake" do not count. Phrases win over their single words: "vielen Dank" is one "vielen dank", not also a "danke". Swear words are shown masked (f***, s***).
  • Tokens are estimates. About 4 characters per token, no tokenizer. "Re-sent" multiplies the polite tokens of a message by the number of model answers that followed in the same chat, because the whole history goes with every call. Most of that is served from the prompt cache, so the dollar figure is an upper bound for uncached input, not a bill.
  • "You're welcome" from the agent is counted only in the first 200 characters of an answer, where it usually stands. That keeps a large history fast.
  • Language. auto picks German or English by the words you use most.

Settings

Set with hermes config set plugins.entries.manners-meter.settings.<key> <value> or in the Desktop plugin settings.

KeyDefaultWhat it does
languageautoauto, en or de
jar_reactionstrueNote to the agent when your message contains a swear word. false = counting only
jar_price1.0Price per coin
currencyemptyEmpty = € in German, $ in English
price_per_mtok3.0Input price per million tokens (USD), only for the uncached upper bound
extra_polite[]Your own polite words
extra_swear[]Your own swear words
excluded_sources[cron, subagent, kanban, batch, webhook, tool]Sources that are not you

Data and privacy

  • Reads state.db of the active profile read only. Never writes to it.
  • Writes only the share card, by default to <HERMES_HOME>/plugin-data/manners-meter/manners-card.html.
  • No network, no model calls, no telemetry.
  • The swear jar note (jar_reactions) is added to your own message through the pre_llm_call hook, never to the system prompt, so the prompt cache stays intact. It names the matched word and the jar count, nothing else. Turn it off with jar_reactions: false.
  • Session titles and message texts never appear in the output or on the card.

Tested

  • 18 offline tests (counting rules, filters, report, slash command, CLI, card, jar hook, timing with 200k character inputs).
  • hermes plugins validate --json: no warnings.
  • Live in an isolated Hermes home (Hermes Agent v0.22.7, Claude Haiku 4.5 over OpenRouter): plugin loaded by the real plugin manager, /manners and hermes manners ran against the new history, the swear jar note reached the model inside the user message and the model answered with "Coin in the jar."
  • Run against one real history (1.6 GB state.db, about 7,600 typed messages, 11,000 cron sessions skipped): about 2 seconds.
  • Not tested yet: Windows, and the slash command on Telegram, Discord and Desktop (same code path, but not seen live).

License

MIT. See LICENSE.

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

More by MadeByBrain

6 plugins by MadeByBrain in the catalog.

MadeByBrainchat-lengthTells the user when a chat is getting too long and hands them a short opener for a fresh chat; the new chat pulls the earlier context itself via session_search, no handover document. Fill level from real provider token counts, measured against Hermes' compaction point by default; notices at 70 % and 90 % (configurable), once each per chat, re-armed after compaction, never in cron, subagent, kanban, batch or webhook runs. Notice in the conversation language, English or German. Disclosure — on the turn that crosses a threshold, pre_llm_call adds a one-turn instruction to that turn's user message (never the system prompt; replayed byte-identical, so prompt caching stays intact); post_api_request stores per-session token counts, model and provider name and which notice fired (no message content) under HERMES_HOME/plugin-data/chat-length/, pruned after 30 days; reads the session title read-only from state.db and the compression settings read-only from config.yaml; no network calls, no tools, no dependencies.Communitytools1MadeByBrainde-lawGerman federal law, EU law and German federal court decisions for Hermes Agent: read one section or article (§ 203 StGB, Art. 6 DSGVO, Art. 50 AI Act) in the source wording with version status (Stand), gazette reference and a ready source line, search the index of federal laws, list a law's sections, and find and read published decisions of BVerfG, BGH, BVerwG, BFH, BAG, BSG and BPatG. Legal texts, not legal advice. Disclosure: sends HTTPS GET requests only to www.gesetze-im-internet.de (law folder names, the daily index, weekly abbreviation lists), www.rechtsprechung-im-internet.de (the daily index, document ids of decisions you read) and publications.europa.eu (CELEX numbers, text language, one SPARQL query per act listing its consolidated versions); section numbers and search words are not sent, because whole laws are downloaded and searched locally. Public sources, no key. Writes public legal texts and indexes (JSON with ETag, Last-Modified and fetch time; no questions, no session data) under HERMES_HOME/plugin-data/de-law/cache, capped by the cache_max_mb setting (default 200 MB). Reads only its own plugin settings. At most one request per second per host, 25 s timeout, 40 MB response cap. rechtsprechung-im-internet.de sends a tdm-reservation header; the plugin fetches its index and single decisions on request only, and case_law: false turns that source off. No hooks, no cron jobs, no background processes. Tools stay on every platform, including gateways (a guest can call them; hermes tools disables one). While the plugin is enabled, its skill adds one line to the skills index of every session.Communitytools1MadeByBrainprivacy-xrayWhere does your data actually go? Records every outgoing model request, the main loop and side tasks such as title generation, compression and vision, as metadata only: destination host, vendor, vendor HQ country, the model vendor behind aggregators such as OpenRouter (read from the model id; the final processing vendor behind an aggregator is not visible), size and counts of detected personal data types (e-mail, IBAN, payment card, phone, IPv4, German Steuer-ID and USt-IdNr, own watch terms). /xray canary invents a fictitious person and /xray trace shows every request and local store that carried it. /xray check audits the config with a severity and the exact hermes config set fix per path; /xray fix <id> --yes applies one; a session retention hint is advice only and is never applied. /xray fix --yes and /xray find run only on local surfaces (CLI, TUI, desktop, dashboard) unless allow_sensitive_on_gateways is turned on. /xray find searches the local stores for a person, /xray report writes a self-contained HTML leak map (no scripts, no external assets) with a before and after view of two canaries; a dashboard tab shows the same page in a sandboxed frame. Not legal advice and not a compliance certificate. Disclosure: no network calls, no model calls, standard library only. pre_api_request and pre_auxiliary_call are observers; they write one metadata line per request (time, session and turn id, task, provider, model, host, vendor, counts, canary id and message fields; never message text or matched values) to HERMES_HOME/plugin-data/privacy-xray/ledger.jsonl (rotated once at ledger_max_mb, default 5 MB). The llm_request middleware is off by default (guard: false); when turned on it masks canary values and watch terms in main model requests before they are sent. Reads the merged Hermes config through load_config_readonly. /xray trace, /xray find and /xray check read outside the plugin's own data, read-only and under a time budget (scan_seconds, default 30): state.db (messages, session titles, stored system prompts, delivery queue), session files including request dumps, memories, logs, cron output, other plugins' plugin-data, paste and pending folders; output shows counts and masked snippets only. Writes config only on /xray fix <id> --yes, through hermes_cli.config.set_config_value (same code as hermes config set); never deletes files. Stores fake canary persons, last check and trace results and requested HTML or Markdown/JSON reports under its plugin-data folder. Registers the tool privacy_xray (map, check, trace, find; read-only, never changes settings), the slash command /xray and a skill that adds one line to the skills index of every session while the plugin is enabled. No credentials, no shell commands, no cron jobs, no background processes, no telemetry.Communitytools1MadeByBrainwriting-guardStyle check for every Hermes answer in German and English: finds em and en dashes outside code, links and quotes (optionally replaces them by rule: ranges and list bullets become hyphens, dashes between words a comma), reports stock AI phrases (German and English) and mixed or switched forms of address (du/Sie) in German. Reports by default with one line appended to the answer; rule based, no model calls. Disclosure — no network calls and no model calls. A transform_llm_output hook reads the final answer of each turn; in report mode it appends one report line when there is a finding, in fix mode it also replaces dashes, with footer: false it never changes the answer; the returned text is what Hermes stores and shows. Stores per chat session id only the last form of address (du or sie) and a timestamp in HERMES_HOME/plugin-data/writing-guard/sessions.json (30 days, at most 2000 sessions); the last report with matched phrases stays in process memory only. Reads only its own plugin settings. Off on cron, subagent, kanban, batch and webhook by default. Registers the tool writing_guard_check (checks a draft, returns JSON), the slash command /writing-guard (settings, last report, check a text) and a skill that adds one line to the skills index of every session while the plugin is enabled.Communitytools1

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section