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.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.00011 | $0.00334 |
| Opus 5 | $0.00005 | $0.00167 |
| Sonnet 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 7d 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.
- 7d ago First seen · 31 lines · 11 tokens per session scan A 2355925b411d
/ss-resume is a command published in the GitHub repository asasugar/SuperSpec (15 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 334 once invoked, about $0.0001 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
iteration-loop
Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no…
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable. Not Done until Phase 5 exit checklist passes.
reverse-spec
Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English).
implement-tasks
A task implementation command that carries out the tasks in a project plan. For code, it can use TDD, a process of writing a failing test before the code that makes it pass; documents and configuration are implemented directly.
constitution
A command for creating or updating a project's constitution: a written set of principles that guides project work. It can take principles directly or explore them interactively.