model-discipline

What model-discipline does

The plugin is based on the idea that, for weaker but faster local models, reliability comes from reducing the action space rather than from cleverer prompts. Instead of letting the model improvise each step, it exposes eight tools: discipline_list_runbooks, discipline_get_runbook, discipline_start_workflow, discipline_status, discipline_execute_stage, discipline_verify, discipline_repair and discipline_publish. The recommended flow is to list runbooks, pick one, start a workflow, execute stages, verify, repair if needed, and publish only when verification is green.

Work is pushed into deterministic scripts, explicit artifacts, explicit workflow state and verifier checks. Runbooks are YAML files authored ahead of time, with stage and verifier scripts, optional templates and fixtures. Two example runbooks ship with it: daily-briefing and repo-inspection-report. Enable the toolset with hermes chat --toolsets model_discipline. Run state is stored under ~/.hermes/model-discipline/. The README says it is intentionally limited and not a general automation framework.

Key features

• Eight tools for listing, starting, executing, verifying, repairing and publishing runbook workflows
• Verifier-first stages with a repair path
• Guarded publication that runs only when verification passes
• YAML runbooks with scripts, templates and fixtures
• Example runbooks: daily-briefing and repo-inspection-report
• Self-tests under tests/

When to use it

• Run a repeatable daily briefing with a small local model
• Generate a repository inspection report from deterministic file inventory
• Author new runbooks for tasks where you do not trust open-ended tool access

Who it is for: Hermes Agent users running smaller local models who want predictable, verifiable workflows.

How it fits with Hermes Agent

Built for Hermes Agent as a plugin that registers a model_discipline toolset, installed under ~/.hermes/plugins/model-discipline.

FAQ