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.svg" alt="Measured on agentmods" 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.02053 |
| Opus 5 | $0.00000 | $0.01026 |
| Sonnet 5 | $0.00000 | $0.00411 |
| Haiku 4.5 | $0.00000 | $0.00205 |
Grade A, and why
restart-dev-env scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sk https://localhost/api/OpenELIS-Global/LoginPage How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Restart Dev Environment
When the user invokes /restart-dev-env (optionally with arguments), perform a
development environment restart workflow with:
- A WAR file rebuild (unless skipped)
- Container restart with force-recreate for the webapp
- Optional database reset (drop volumes with
--full-reset) - E2E test fixture loading (by default)
- Let's Encrypt setup (only for non-localhost domains)
This command is action-oriented: it builds and restarts by default. Use flags to skip steps when iterating quickly. The command reports progress at each checkpoint so you can monitor the restart process.
User Input
$ARGUMENTS
Interpret arguments best-effort. Support these patterns:
/restart-dev-env→ Full restart (build WAR, restart containers, load fixtures)/restart-dev-env --full-reset→ Drop database volumes before restart (clean slate)/restart-dev-env --skip-build→ Skip WAR rebuild (use existing target/OpenELIS-Global.war)/restart-dev-env --skip-fixtures→ Skip loading E2E test fixtures- Combine flags as needed:
/restart-dev-env --full-reset --skip-build
If any inputs are unclear, ask a single concise question and continue with safe defaults.
Safety Rules (non-negotiable)
- Warn if there are uncommitted changes (but proceed unless user stops).
- Never drop database volumes unless
--full-resetis explicitly passed. - Always wait for webapp readiness before loading fixtures.
- Report container status after restart (even if some containers fail).
- If Let's Encrypt generation fails, warn but continue (use self-signed certs).
Workflow
0) Preflight (gather facts, no changes yet)
Run these and summarize the results:
git rev-parse --show-toplevel(verify project root)- Load .env if present (so dev servers with a domain use it):
Thenset -a; [ -f .env ] && . ./.env; set +aLETSENCRYPT_DOMAINandLETSENCRYPT_EMAILfrom .env are available for the rest of the workflow. If .env is missing, both vars are unset; DOMAIN then uses the default below (same asscripts/reset-dev-env.sh). git status --porcelain(warn if uncommitted changes)- Check
LETSENCRYPT_DOMAINenv var (default:analyzers.openelis-global.orgwhen unset, so hosted dev envs get the right domain even without .env) - Check
LETSENCRYPT_EMAILenv var (required for Let's Encrypt cert generation)
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 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 (251 stars, last pushed today), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 2,053 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.