Borrowing it
Nothing to install: this file belongs to asasugar/SuperSpec. 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/asasugar/SuperSpec/master/.cursor/commands/ss-resume.mdgit clone --depth 1 https://github.com/asasugar/SuperSpecWrote 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/asasugar/superspec/ss-resume)<a href="https://agentmods.dev/commands/asasugar/superspec/ss-resume"><img src="https://agentmods.dev/badge/commands/asasugar/superspec/ss-resume/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/asasugar/superspec/ss-resume"><img src="https://agentmods.dev/badge/commands/asasugar/superspec/ss-resume.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.00011 | $0.00334 |
| Opus 5.5 | $0.00004 | $0.00134 |
| Sonnet 5.5 | $0.00002 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
/ss-resume 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 1mo 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
Guardrails
- Use when returning to a change after a break
- Read only context.md by default (minimal tokens), other docs are user's choice
Steps
- Locate current change folder:
{specDir}/changes/ - Run
superspec sync <name>to collect latest git changes into context.md - Read
context.md(single file, contains: goals, progress, strategy, input, git changes) - Determine behavior mode from
strategyin context.md (follow / create) - Report current state: goals, progress, git changes, affected files
- Ask user whether to read additional docs, list available files in change dir, suggest priority:
- ✅
tasks.md(recommended, task details and dependencies) proposal.md(requirements and solution review)spec.md(Boost mode, requirement details)design.md(architecture decisions)checklist.md(quality check results)clarify.md(historical Q&A)
- ✅
- Read selected files based on user's choice
- Ask user: what needs fixing / adjusting?
- Fix respecting
strategy(follow = obey conventions / create = may explore new approaches) - After fix: update tasks.md checkbox if applicable
- Run
superspec sync <name>to refresh context.md
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.
- 1mo ago First seen · 31 lines · 11 tokens per session scan A 2355925b411d
/ss-resume is a command published in the GitHub repository asasugar/SuperSpec (18 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 334 once invoked, about $0.0000 per session on Opus 5.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
CHANGELOG
All notable changes to the @mstar-harness/commands package are documented in this file.
feature-00c-resume
Retoma execucao feature-00c pausada por bloqueio humano ou schedule entre ondas. Valida hash (FR-014 + FR-PRE-004), aplica resposta a bloqueios, delega proxima onda ao agente-00c-feature-orchestrator.
iteration-loop
Run a whole iteration Phase 1→6 autonomously — code-first direction lock with a retained prototype, then execute → close → PR → merge-ready → post-merge close. Optional direction hint and scale S|M|L|XL; explicit autonomous opt-in, no grill-me, no routine confirmation.
amazing-e2e-check
Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
reverse-spec
A command for reverse specification: examining an existing project and producing documentation that describes its behavior and design.