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-tasks.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-tasks)<a href="https://agentmods.dev/commands/asasugar/superspec/ss-tasks"><img src="https://agentmods.dev/badge/commands/asasugar/superspec/ss-tasks/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-tasks"><img src="https://agentmods.dev/badge/commands/asasugar/superspec/ss-tasks.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.00010 | $0.00182 |
| Opus 5.5 | $0.00004 | $0.00073 |
| Sonnet 5.5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
/ss-tasks 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
- Read proposal.md first (and spec.md in boost mode)
- Tasks must be small, verifiable, and actionable (< 1 hour each in boost mode)
- Group related changes to the same file under one task
- Include verification steps for each task
Steps
- Read
{specDir}/changes/<name>/proposal.md - If boost mode, also read
spec.md - Read
{specDir}/templates/tasks.mdas structural reference - Directly generate tasks.md (with real task content, not template placeholders)
- Each task should have: clear description, file paths, dependencies, verification criteria
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 · 21 lines · 10 tokens per session scan A 0fa663604594
/ss-tasks is a command published in the GitHub repository asasugar/SuperSpec (18 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 182 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
iteration-drive
Drive or resume the selected locked iteration through Phase 2→6 — autonomous execute → iteration-close → PR → merge-ready loop → post-merge close. Takes no arguments.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
auto-dev
A command that autonomously develops each pending requirement in a shared product blueprint using a requirements-first software-development process.
blueprint
A command for discussing and maintaining confirmed product requirements in one shared product blueprint.
design-to-plan
A command that turns an approved design into a traceable implementation plan. It can use project language settings for the conversation and for generated requirement, specification, plan, and task documents.
feature-00c-abort
Aborta manualmente feature-00c para um short-name. SIGTERM + grace period 60s para persistir state; force-acquire do lock como fallback (FR-025). Marca abortada, gera relatorio parcial, commit local. Idempotente.