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/skills/overview/commands/speckit.overview.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/speckit.overview)<a href="https://agentmods.dev/commands/digi-uw/openelis-global-2/speckit.overview"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/speckit.overview.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.00085 | $0.01104 |
| Opus 5 | $0.00043 | $0.00552 |
| Sonnet 5 | $0.00017 | $0.00221 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
speckit.overview 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/speckit.overview
Goal
Produce a single self-contained interactive HTML canvas (overview.html) that surfaces a SpecKit feature's dense markdown content in 2-level progressive disclosure — overview KPIs, user stories, milestones, data model, decisions, API, testing, and inline-rendered spec files — with light + dark mode and auto-deployment to GitHub Pages.
The canvas is the stakeholder-friendly entry point for the feature: reviewers, designers, PMs, and onboarding engineers all start here, then drill into the source .md files for detail.
Execution
Step 1 — Determine SPEC_DIR
If the user provided a path, use it. Otherwise, auto-detect:
# Option A: from current git branch (feat/ogc-285-* → specs/OGC-285-*)
BRANCH=$(git branch --show-current)
# Option B: from most-recently-modified specs/<dir>
SPEC_DIR=$(ls -td specs/*/ | head -1)
Confirm <SPEC_DIR>/spec.md exists. If not, abort with an instructive message.
Step 2 — Extract canvas data
python3 .specify/oe/skills/overview/scripts/extract-spec-data.py <SPEC_DIR>
Writes <SPEC_DIR>/canvas/canvas-data.json (created if missing). Stdout reports counts of stories / milestones / tables / endpoints / clarifications / divergences / files / commits / ACs found.
Step 3 — Build the canvas
python3 .specify/oe/skills/overview/scripts/build-canvas.py <SPEC_DIR>
Assembles templates/canvas.html.template + canvas-data.json → <SPEC_DIR>/canvas/overview.html. Substitutes the {{*_JSON}} placeholders with the extracted data.
Step 4 — Verify locally
open <SPEC_DIR>/canvas/overview.html # macOS
xdg-open <SPEC_DIR>/canvas/overview.html # Linux
Check:
- All visible tabs render (Overview / Stories / Data Model / Roadmap / Decisions / API / Testing / Spec Files / PR + Commits)
- Tabs with no data are hidden (per hide-when-empty rules)
- Light/dark mode toggle in the top-right works + persists across reloads
- Spec Files tab renders the underlying markdown inline (sidebar list + main content pane)
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 · 102 lines · 85 tokens per session scan A ee50d07643d8
speckit.overview is a command published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (251 stars, last pushed yesterday), licensed MPL-2.0. It adds 85 tokens to every session and 1,104 once invoked, about $0.0004 per session on Opus 5. 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.
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.