Borrowing it
Nothing to install: this file belongs to DIGI-UW/OpenELIS-Global-2. 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/DIGI-UW/OpenELIS-Global-2/develop/.specify/oe/commands/restart-dev-env.mdgit clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2Wrote 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/digi-uw/openelis-global-2/restart-dev-env)<a href="https://agentmods.dev/commands/digi-uw/openelis-global-2/restart-dev-env"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/restart-dev-env/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/digi-uw/openelis-global-2/restart-dev-env"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/restart-dev-env.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.00399 |
| Opus 5.5 | $0.00000 | $0.00160 |
| Sonnet 5.5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
restart-dev-env 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 8d 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
Restart Development Environment
When the user invokes /restart-dev-env, use the supported development launcher
from the owning checkout. Do not invent Compose layering, load SQL fixtures, or
choose a domain for the user.
$ARGUMENTS
Inspect the checkout and its changes, then run:
scripts/dev-stack doctor
scripts/dev-stack up
scripts/dev-stack status
scripts/dev-stack url
up builds the current source WAR, pulls the published development images
(it never builds images unless --build is passed), recreates the running
backend, waits for login readiness and prepares development scenarios through
application services. It preserves existing data. The launcher reads .env and
owns local or public-domain certificate setup; a missing public-domain setting
must not silently target a shared server.
Supported options:
--skip-build: pass todev-stack upto reuse this checkout's already-built WAR and the application images the lastupran. Missing artifacts must fail.--build: only when the user asks for it or the change needs it (frontend dependencies, Dockerfiles, Bridge or mock source), pass todev-stack upto build the application images from the checkout.--full-reset: only when explicitly requested, runscripts/dev-stack down --volumes --yesbeforeup. This deletes the owning development stack's data.--skip-fixtures: obsolete; this path never loads SQL test fixtures. Usedev-stack up --no-scenariosif the user wants to skip application scenarios.
Stop and report a failed build, readiness or certificate operation. Show relevant
logs through scripts/dev-stack logs; do not report success after a failed step.
For CI reproduction, use scripts/run-ci-checks.sh --job NAME. A development restart is not CI validation.
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.
- 8d ago Changed · +5 lines 9fd16381df75
- 17d ago Changed · -227 lines 63ee669d4ebf
- 1mo ago First seen · 266 lines · 0 tokens per session scan A cd007ef4c17a
restart-dev-env is a command published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (272 stars, last pushed today), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 399 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-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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.