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-analyzer-harness.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-analyzer-harness)<a href="https://agentmods.dev/commands/digi-uw/openelis-global-2/restart-analyzer-harness"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/restart-analyzer-harness/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-analyzer-harness"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/restart-analyzer-harness.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.02391 |
| Opus 5 | $0.00000 | $0.01196 |
| Sonnet 5 | $0.00000 | $0.00478 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade A, and why
restart-analyzer-harness 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 11d 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.
# Analyzer count (authenticated curl) How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Restart Analyzer Harness
When the user invokes /restart-analyzer-harness (optionally with arguments),
restart the analyzer harness test environment using the project's own scripts.
This skill delegates to reset-env.sh — the authoritative harness lifecycle
script. It handles compose layering, bootstrap, plugin staging, fixture loading,
analyzer seeding, and Let's Encrypt setup. Do NOT reimplement these steps inline
— the scripts already handle edge cases (compose-stack.sh layering, credential
defaults, submodule init, checksum clearing, etc.).
User Input
$ARGUMENTS
Interpret arguments best-effort. Support these patterns:
/restart-analyzer-harness→ Default:reset-env.sh --full-reset/restart-analyzer-harness --full-reset→ Drop database volumes (clean slate)/restart-analyzer-harness --skip-fixtures→ Skip fixture and analyzer seeding/restart-analyzer-harness --build→ Build WAR before restarting/restart-analyzer-harness --letsencrypt→ Add LE compose overlay/restart-analyzer-harness --skip-letsencrypt→ Skip LE even when env is set/restart-analyzer-harness --ci-parity→ Bring up the CI-parity stack (build.docker-compose.yml+.github/ci/ci.analyzer-harness.yml) instead of the local dev stack. Selects frontend Dockerfiletarget: runtime(nginx serving minifieddist/) — the exact image CI runs. Use this to locally reproduce CI E2E failures (e.g. React #130-class regressions that only fire under the production bundle) before pushing. Implicitly forces--skip-letsencrypt(CI compose files don't include the LE overlay).- Combine flags as needed
Safety Rules (non-negotiable)
- Warn if other Docker containers using ports 80/443/8443/15432 are running.
- Never drop database volumes unless
--full-resetis explicitly passed. - Always wait for webapp readiness before declaring success.
- NEVER modify, regenerate, or replace password hashes anywhere.
Architecture (read this — do NOT hardcode compose files)
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.
- 11d ago First seen · 218 lines · 0 tokens per session scan A 08936e254121
restart-analyzer-harness is a command published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (252 stars, last pushed yesterday), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 2,391 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.
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.