Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/emadd/mise-en-claudeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/emadd/mise-en-claude/mise-update)<a href="https://agentmods.dev/commands/emadd/mise-en-claude/mise-update"><img src="https://agentmods.dev/badge/commands/emadd/mise-en-claude/mise-update/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/emadd/mise-en-claude/mise-update"><img src="https://agentmods.dev/badge/commands/emadd/mise-en-claude/mise-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00752 |
| Opus 5 | $0.00016 | $0.00376 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade C, and why
mise-update scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
5. **Clean up** the temp clone (`rm -rf "$TMP"`). **Leave** any `.bak-<time>` files the installer What it actually says
You are running /mise-update — it refreshes the installed mise commands (/mise-init,
/mise-cook, /mise-handoff, /mise-clean, plus WORKFLOW-ORCHESTRATION.md and mise-PROMPT.md)
to the latest published version. This updates the tool itself; it is not /mise-init's
Update mode, which refreshes a project's mise en place.
The one rule that makes this correct: mise's install.sh copies from whatever checkout it lives
in — it never consults the remote. So you must install from a fresh clone of the canonical
main, not from any working copy that happens to be on disk. Installing from a local repo is how
un-pushed, half-finished work gets shipped by accident — the exact bug this command exists to
prevent. Never run an install.sh you find in the current directory or the user's mise repo.
Do exactly this:
-
Resolve scope and ref. Default scope is global (
~/.claude). If$ARGUMENTScontains--project [dir], pass that through to the installer instead. Default ref ismain; if$ARGUMENTSnames another branch/ref, use it. Canonical source:https://github.com/emadd/mise-en-claude.git. -
Clone the published version into a throwaway temp dir (never the user's project or repo):
TMP="$(mktemp -d)" git clone --depth 1 --branch main https://github.com/emadd/mise-en-claude.git "$TMP"If the clone fails (offline / network), STOP and tell the user — do not fall back to any local checkout.
-
Show what "latest" resolved to:
git -C "$TMP" log --oneline -1, so the user sees the exact published commit before anything is written. -
Run that clone's installer, non-interactively, for the resolved scope:
"$TMP/install.sh" -y # global (~/.claude) — the default "$TMP/install.sh" -y --project <dir> # only if the user asked for project scopeThe installer is non-destructive: it backs up any differing file as
.bak-<time>and leaves identical files untouched, so re-running is safe and idempotent. -
Clean up the temp clone (
rm -rf "$TMP"). Leave any.bak-<time>files the installer created — those are the user's rollback copies — and tell them the paths so they can delete them once satisfied. -
Summarize the result: the published commit installed, which files were updated (
+/~) vs. already current (=), where any backups landed, and remind the user to restart Claude Code to pick up refreshed commands.
Never touch the user's own mise working repo, its branches, or its uncommitted changes — this
command updates the installed copies only, always from the published main.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 53 lines · 0 tokens per session scan C c644aa84d23a
mise-update is a command published in the GitHub repository emadd/mise-en-claude (51 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 752 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.