Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From ultracost
Diffs the estimated cost of two workflow versions and judges whether the change is worth it. Supports --ci for a PR-comment markdown table.
How this command is triggered — by the user, by Claude, or both
Slash command
/ultracost:diff <old-script.js> <new-script.js>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# ultracost diff You are running the **diff** workflow. Goal: explain how an edit changed the cost and whether that is justified. 1. Take two paths from `$ARGUMENTS` (old, then new). 2. Gather evidence: 3. Interpret the delta (tiered cost + agent count): what drove it, and is it a reasonable trade for the capability gained? If this is for a pull request, re-run with `--ci` to emit the Infracost-style markdown table and hand that back. ## How to present this The CLI output is your **evidence** — its panels, tables, and bars (in color, since `FORCE_COLOR` is set) are shown to th...
You are running the diff workflow. Goal: explain how an edit changed the cost and whether that is justified.
$ARGUMENTS (old, then new).env -u NO_COLOR FORCE_COLOR=3 node "${CLAUDE_PLUGIN_ROOT}/bin/cli.js" diff <old> <new>
--ci to
emit the Infracost-style markdown table and hand that back.The CLI output is your evidence — its panels, tables, and bars (in color, since
FORCE_COLOR is set) are shown to the user in the command-output view; don't just
re-echo them, and don't strip them either. Lead with your reasoning and the recommended
action. When you offer choices, use the AskUserQuestion tool so the user gets a native
picker, then carry out what they choose. Keep prose tight.
/diffCompares security scans between git refs <base-ref> [<head-ref>], reports new/fixed vulnerabilities, severity changes, regression score, and attack surface diffs.
/diffCompresses a git diff — keeps real code hunks intact, collapses lockfile/generated/minified/vendor diffs to a one-line summary. Accepts a diff file or piped input.
npx claudepluginhub danielkremen818/ultracost --plugin ultracost