Borrowing it
Nothing to install: this file belongs to Proxy2021/Enso. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Proxy2021/Enso/main/.claude/commands/enso-deploy.mdgit clone --depth 1 https://github.com/Proxy2021/EnsoWrote 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/proxy2021/enso/enso-deploy)<a href="https://agentmods.dev/commands/proxy2021/enso/enso-deploy"><img src="https://agentmods.dev/badge/commands/proxy2021/enso/enso-deploy/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/proxy2021/enso/enso-deploy"><img src="https://agentmods.dev/badge/commands/proxy2021/enso/enso-deploy.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.00000 | $0.00681 |
| Opus 5.5 | $0.00000 | $0.00272 |
| Sonnet 5.5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
enso-deploy scanned grade A with 0 findings 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 2mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Merge, build, commit, push, update docs if needed, and restart all Enso services.
⛔ If you are running inside the Enso gateway (spawned via the Enso mobile/web client for bug fixing, auto-repair, or debug reporter) — do NOT run this command. Restarting the gateway kills your own session. Just fix the code and stop.
Steps
-
Merge worktree to main: If we're on a worktree branch (not
main), merge the current branch intomainusinggit merge <branch> --no-editfrom the main repo. If already on main, skip. -
Build: Run
npm run buildfrom the project root to produce the production frontend bundle. -
Assess whether docs need updating: Review the recent commits (
git log main -10 --oneline) and the conversation context. Determine if a major feature or design change was introduced — something that materially changes what the project does or how it presents itself. Minor fixes, refactors, and small tweaks do NOT require doc updates.Examples that warrant doc updates:
- New built-in app or tool family added
- Major new capability (e.g. live sharing, voice input, mobile app support)
- Fundamental architecture change
- New user-facing workflow or integration
Examples that do NOT:
- Bug fixes, style tweaks, performance improvements
- Internal refactors that don't change user-facing behavior
- Adding a button or fixing a dialog
-
Update docs (only if step 3 determined it's needed): Review and update the following files as needed to reflect the new capability. Keep changes concise — add or revise only what's relevant to the new feature, don't rewrite unrelated sections.
README.md— Update the Features list, Built-in Apps section, or tagline if the change is significant enough. Add a new subsection under Built-in Apps if a new app was added. Update the features bullet list if a new major capability was introduced.package.jsondescriptionfield — Only if the project's one-liner description no longer captures what the project does.- GitHub repo description — Run
gh repo edit --description "..."only if the package.json description changed. CLAUDE.md— Update the Vision, Key Concepts, or Architecture sections only if the change affects how developers should understand the codebase.
-
Commit (if needed): On the
mainbranch, checkgit statusfor any uncommitted changes (build output, doc updates). If there are changes, stage and commit them. Use a commit message likedocs: update README/description for <feature>if docs changed, or a short descriptive message for build-only changes. -
Push: Run
git pushto push main to the remote. -
Restart services: Run the restart script for the current platform:
- macOS:
./restart.shfrom the project root - Windows:
powershell -ExecutionPolicy Bypass -File restart.ps1
- macOS:
Report the result of each step. If any step fails, stop and report the error.
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.
- 2mo ago First seen · 40 lines · 0 tokens per session scan A 522e5c329282
enso-deploy is a command published in the GitHub repository Proxy2021/Enso (6 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 681 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
issue-to-mr-setup
Create an automation that implements GitLab issues when a configurable trigger label is applied. Polls one or more projects deterministically, clones the default branch, starts one OpenHands conversation per label event, then commits, pushes, and opens the merge request itself.
run-plan
Execute implementation plan phases for a change.
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.