add-habitAdd a new habit to your own habits — a standing rule for how the agent should behave across all work, or whenever a stated trigger applies — with a one-line summary that sits in every session. Writes ~/.claude-user-data/habits/<id>.md, reinstalls the CLAUDE.md block and syncs. Use when the user stat
adopt-habitAdopt a habit from the example library into your own habits — copies it to ~/.claude-user-data/habits/, fills in tunable values such as a spend limit, records which library version it came from, then reinstalls the CLAUDE.md block. Use when the user wants one of the example habits, asks "what habits
check-habitsValidate your habits and SOPs — they parse, summaries are present and faithful to their full text, no two habits overlap or contradict, nothing is filed as the wrong kind, the user-data repo is committed, and adopted habits are up to date with the library. Use after editing habits or SOPs, before tr
context-checkVerify the user-level CLAUDE.md is wired correctly to your habits and SOPs — exactly one generated agent-habits block, in index mode, under its size budget, matching the current habit and SOP files, with no legacy or hand-written duplicates — and repair drift by reinstalling. Use when asked to "chec
install-habitsInstall or update the generated agent-habits block — your habits' summary lines and SOP trigger lines — in ~/CLAUDE.md, or put full habit texts (a subset, inline) into a project CLAUDE.md or AGENTS.md that others read. Marker-delimited, idempotent, backs the file up, and leaves hand-written prose al
list-habitsList your habits — ids and one-line rules, optionally retired ones — or the example library you can adopt from, or find which habit covers something. Use when asked "what are my habits", "list habits", "what habits are available", "which habit covers X", or before deciding whether something is alrea
reconcile-habitsCompare a system prompt file against your habits and SOPs and resolve the drift in both directions — prose in ~/CLAUDE.md that should become a habit file, habit files whose installed copy is stale, and hand-written sections now duplicated by the managed block. Produces a reconciliation report and ap
remove-habitRetire one of your habits so it stops being installed, or delete it outright when explicitly asked — then reinstall the CLAUDE.md block and sync. Use when the user says to drop, remove, delete, retire or stop applying a habit.
setupFirst-time setup of Agent-Habits — create the private user-data folder for your own habits and SOPs, optionally adopt habits from the library, put it under git with a private remote, and add the one generated block to the user-level CLAUDE.md. Also covers a second machine (clone the existing user-da
share-habitContribute one of your own habits to the public example library in the Agent-Habits plugin repo — depersonalised, with tunable values turned into variables — so others can adopt it. Use when the user says a habit might be useful to others, asks to publish or share a habit, or after add-habit produce
sop-editAmend an existing SOP — fix a step that has drifted, add a failure mode that was just hit, adjust its trigger or autonomy, or re-date last_verified after a successful run. Use when the user says an SOP is out of date or wrong, when following one produced a surprise, and routinely at the end of any S
sop-listShow what is in the SOP library — everything, or filtered by tag, or only the procedures that have gone stale. Use when the user asks what SOPs they have, whether one exists for something, which ones need reviewing, or wants an overview of their procedures before deciding what to write next.
sop-removeRetire an SOP that no longer applies — moving it to the library's archive, or deleting it outright when asked. Use when the user says a procedure is obsolete, that they do not do it that way any more, or that a system it depends on is gone; and when a replacement SOP has been written for the same jo
sop-runFind the user's standard operating procedure for the task at hand and follow it. Reads the SOP index, matches the situation, opens exactly one procedure and executes it at the autonomy level that SOP declares. Use whenever a multi-step recurring task comes up — deploying, publishing, filing, orderin
sop-writeCapture a recurring procedure as a new SOP in the user's library — usually written from what just happened in this session, while the details are still known. Use when the user says "write this up as an SOP", "remember how we did this", "add this to my procedures", or when the same multi-step sequen
syncCommit and push your habits and SOPs (the ~/.claude-user-data repo), or pull them onto this machine, then reinstall the CLAUDE.md block so it matches. Use when the user asks to sync, save, push or back up habits or SOPs, when setting up a second machine, and at the end of any session that added or c
update-habitRevise one of your habits — its rule, summary, trigger, exceptions or values — then reinstall the CLAUDE.md block and sync. Use when the user corrects how a standing habit should work, sharpens or loosens one, or says a habit's one-line summary misleads. Also for pulling in a newer library version o