All plugins

crontab-ref

@crontab: context references that explain a cron expression for the model: @crontab:"0 9 * * 1-5" (or a shortcut such as @crontab:@daily) attaches a plain-words reading ("At 09:00 on Monday through Friday."), each field on its own row, whether Hermes's /cron takes it as a cron expression (shortcuts, ? and 5#3 are not), its next five runs in Hermes's timezone setting worked out the way cron/jobs.py computes next runs, and notes on day of month OR day of week, * in the minute field, steps that do not divide the hour or day, days 29-31 and 7 as Sunday; the TUI and Desktop composer suggest examples and preview an expression as you type it. The reading comes from croniter, the library Hermes's scheduler uses. Disclosure — reads only the text of the reference itself, the system clock and Hermes's timezone setting (HERMES_TIMEZONE, else timezone from the loaded config through hermes_cli.config), using croniter (already installed with Hermes) and Python's standard library; no network, no files read or written, no subprocess, no credentials read, no cron job created, changed or run; the @crontab: reference and its explanation become part of the message sent to your model provider and saved in the session history; register() only adds the @crontab: reference provider.

olric3015Toolsv1.0.0Updated 28 days ago

About

@crontab: context references that explain a cron expression for the model: @crontab:"0 9 * * 1-5" (or a shortcut such as @crontab:@daily) attaches a plain-words reading ("At 09:00 on Monday through Friday."), each field on its own row, whether Hermes's /cron takes it as a cron expression (shortcuts, ? and 5#3 are not), its next five runs in Hermes's timezone setting worked out the way cron/jobs.py computes next runs, and notes on day of month OR day of week, * in the minute field, steps that do not divide the hour or day, days 29-31 and 7 as Sunday; the TUI and Desktop composer suggest examples and preview an expression as you type it. The reading comes from croniter, the library Hermes's scheduler uses. Disclosure — reads only the text of the reference itself, the system clock and Hermes's timezone setting (HERMES_TIMEZONE, else timezone from the loaded config through hermes_cli.config), using croniter (already installed with Hermes) and Python's standard library; no network, no files read or written, no subprocess, no credentials read, no cron job created, changed or run; the @crontab: reference and its explanation become part of the message sent to your model provider and saved in the session history; register() only adds the @crontab: reference provider.

crontab-ref

@crontab: references for Hermes: put @crontab:"0 9 * * 1-5" in a message and Hermes
replaces it with what that cron expression means, worked out on your machine: a sentence in
plain words, each field on its own row, whether Hermes's /cron accepts it, its next five runs
in Hermes's timezone, and notes for the cases people usually get wrong.

Cron expressions are short and easy to misread, for people and for models: 0 9 1 * 1 does not
mean "the first Monday", * 9 * * * runs sixty times, */7 does not run every seven minutes
across the hour, and @daily is not something Hermes's /cron takes. The model gets the
reading already done, by the same library Hermes's scheduler uses, instead of working it out in
its head.

Install

hermes plugins install crontab-ref --enable

Requires Hermes 0.21.5 or newer. No API key, no configuration. It uses croniter, which Hermes
already installs for its own scheduler; nothing else is installed.

Use

@crontab:"0 9 * * 1-5"      five fields: minute hour day-of-month month day-of-week
@crontab:"*/15 9-17 * * *"  steps, ranges and lists
@crontab:"0 9 * * MON-FRI"  month and weekday names
@crontab:"0 9 L * *"        L (last day of the month), L5 (last Friday), 5#3 (third Friday)
@crontab:"* * * * * 30"     a 6th field (seconds) and a 7th (year), as croniter reads them
@crontab:@daily             the shortcuts @yearly @annually @monthly @weekly @daily @midnight @hourly

An expression has spaces, so it goes in quotes (", ' or a backtick); Hermes reads a
reference up to the end of the line. A shortcut such as @daily needs no quotes.

Example, from the end-to-end test (one-shot hermes chat turns run on 2026-10-24 with
timezone: Asia/Kolkata in config.yaml). The message When does this fire? @crontab:"0 9 * * 1-5" reaches the model as the message followed by:

Cron expression "0 9 * * 1-5", as Hermes's scheduler (croniter) reads it
  At 09:00 on Monday through Friday.
  minute        0    0
  hour          9    9
  day of month  *    any
  month         *    any
  day of week   1-5  Monday through Friday
Hermes /cron: accepted as a cron expression
Next 5 runs, in Asia/Kolkata (Hermes's timezone setting)
  Mon 2026-10-26 09:00 +05:30  in 1 day 14 hours
  Tue 2026-10-27 09:00 +05:30  in 2 days 14 hours
  Wed 2026-10-28 09:00 +05:30  in 3 days 14 hours
  Thu 2026-10-29 09:00 +05:30  in 4 days 14 hours
  Fri 2026-10-30 09:00 +05:30  in 5 days 14 hours

From the same run, @crontab:@daily says that /cron needs the five fields:

Cron expression "@daily", as Hermes's scheduler (croniter) reads it
  At 00:00 every day.
  same as 0 0 * * *
  ...
Hermes /cron: Hermes's /cron does not take @daily; write the five fields instead: 0 0 * * *

and @crontab:"*/7 * * * *" ends with:

Notes
  - */7 in the minute field starts again every hour: after :56 the next run is :00, 4 minutes later, not 7

What the notes point out:

  • Day of month and day of week both set (0 9 1 * 1): a day that matches either one runs,
    so this is "the 1st, and every Monday", not "the 1st if it is a Monday". croniter applies
    this rule to */2 too.
  • * in the minute field with a set hour (* 9 * * *): every minute of that hour.
  • A step that does not divide the hour or the day (*/7, 0 */5 * * *): the gap at the
    turn of the hour or the day is shorter.
  • Days 29-31: months without that day are skipped; L is the last day of every month.
  • 7 in day of week is Sunday, the same as 0.
  • A date that never comes (0 9 31 2 *): no runs are listed and the block says so.

How it is read

  • The fields are expanded by croniter (croniter.expand), the library Hermes's /cron
    scheduler uses, and the sentence is written from that expansion.
  • "Hermes /cron" repeats the check in Hermes's cron/jobs.py::parse_schedule: the first five
    fields may only use digits, letters and * , - / (so ? and 5#3 are not taken as cron
    there), and croniter must read the expression. Shortcuts like @daily are not taken either.
  • The next runs are worked out like cron/jobs.py::compute_next_run: croniter walks the wall
    clock of Hermes's timezone setting (timezone in config.yaml, or HERMES_TIMEZONE), so a
    09:00 job stays at 09:00 across a daylight-saving change. With no timezone set, it is this
    computer's local time, and the block says so.

Suggestions

In the TUI and the desktop app, typing @crontab: suggests three example expressions with their
meaning, and @crontab: followed by an expression previews it (@crontab:@daily shows @daily = At 00:00 every day.). The classic CLI does not show reference suggestions.

Security and footprint

  • register() only registers one context reference provider (@crontab:).
  • It reads the text of the reference, the system clock, and Hermes's timezone setting
    (HERMES_TIMEZONE, else timezone from the loaded config through hermes_cli.config), and
    only when you write @crontab: in a message.
  • No network access, no subprocesses, no downloads, no credentials read, no files written. It
    does not create, change or run any /cron job.
  • Uses croniter (already installed by Hermes) and the standard library.

Development

python -m pip install "pytest>=8,<10" "croniter>=6,<7"
python -m pytest tests                                               # unit tests, no Hermes needed
PYTHONPATH=<hermes checkout> python tests/e2e/crontab_ref_e2e.py      # real hermes chat turns, Hermes's scheduler, TUI suggestions
hermes plugins validate crontab-ref

Changes

  • 1.0.0: first release.

MIT licensed.

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

More by olric3015

18 plugins by olric3015 in the catalog.

olric3015approval-ledgerLocal ledger of Hermes's approval prompts (dangerous commands, protected writes, MCP consent, smart-mode verdicts): /approval-log shows how often each rule asked, how many prompts were approved, denied or left unanswered, and how long a person took to answer, per rule, per surface or per day, for the last 24 hours, any number of hours or days, the latest session or everything recorded; /approval-log recent lists the newest decisions (ten, or up to 100 with /approval-log recent 50). Disclosure — writes decision metadata (session id, surface, rule label, answer, timings; no command, description or session key) to plugin-data/approval-ledger/approvals.jsonl, trimmed to 5,000 rows past 2 MB; observer only, cannot answer or change an approval; no networkCommunitytoolsolric3015aux-ledgerLocal ledger of Hermes's auxiliary LLM calls (titling, compression, vision, approval): /aux shows tokens, time and failures per task, model, provider or day, or lists the newest calls (ten, or up to 100 with /aux recent 50), for the last 24 hours, any number of hours or days, the latest session or everything recorded. Disclosure — writes auxiliary-call metadata (ids, models, timings, token counts, no prompt or response text) to plugin-data/aux-ledger/calls.jsonl, trimmed to 5,000 rows past 2 MB; no networkCommunitytoolsolric3015b64-ref@b64: context references that decode encoded text for the model: @b64:<value> takes base64 (standard or URL-safe, padded or not), hex (0x48656c6c6f, 48:65:6c, \x48\x65), percent-encoding or a data: URI, told apart by the value's shape or picked with base64:, base64url:, hex: or url:, and attaches what it holds: text as text with control and invisible characters escaped, JSON pretty-printed, gzip and zlib inflated in memory (at most 1 MiB, one layer), and binary named by its format (PNG and GIF with their size, JPEG, PDF, ZIP, ELF, SQLite and more) with a hex dump of its first 128 bytes; notes point out a value that was cut short, padding that is off, a second layer of encoding and a JWT inside; the TUI and Desktop composer preview a value as you type it. Disclosure — reads only the text of the reference itself, using Python's base64, json, urllib.parse and zlib; nothing decoded is run, opened or saved; no network, no files read or written, no subprocess, no credentials read; the plugin keeps no copy of what it decodes, but the @b64: reference and the decoded contents become part of the message sent to your model provider and saved in the session history, so decode only values you are willing to share with it; register() only adds the @b64: reference provider.Communitytoolsolric3015chmod-ref@chmod: context references that explain a file permission mode for the model: @chmod:<mode> takes an octal mode (755, 0755, 4755), ls -l text (-rwsr-xr-x, with the file type letter and a trailing + . or @) or an st_mode as stat and git write it (100644), and attaches both forms, each class's rights in words (directory rights named as such), what setuid, setgid and the sticky bit do and where they are ignored, and notes such as a mode everyone can change, one private to the owner, or a class holding rights the class before it lacks; @chmod:"644 u+x,go-w" applies a symbolic change step by step the way GNU chmod does (u g o a, + - =, r w x X s t, copies like u=g), @chmod:"100644 100755" shows what changes between two modes, and @chmod:"umask 027" shows what new files and directories get; the TUI and Desktop composer preview a mode as you type it. Disclosure — reads only the text of the reference itself, using Python's re; it never looks at a file on disk; no network, no files read or written, no permission changed, no subprocess, no credentials read; the plugin keeps no copy of what you write, but the @chmod: reference and the explanation become part of the message sent to your model provider and saved in the session history; register() only adds the @chmod: reference provider.Communitytools

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section