Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/gotalab/cc-sdd/spec-quickgit clone --depth 1 https://github.com/gotalab/cc-sddWhat 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 | $0.00008 | $0.02630 |
| Opus 5 | $0.00004 | $0.01315 |
| Sonnet 5 | $0.00002 | $0.00526 |
| Haiku 4.5 | $0.00001 | $0.00263 |
Grade A, and why
spec-quick 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 3d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- kiro-spec-quick — 98% identical, 26 lines differ
- spec-quick — 91% identical, 68 lines differ
- spec-quick — 91% identical, 68 lines differ
- spec-quick — 91% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Spec Generator
<background_information>
- Mission: Execute all spec phases (init → requirements → design → tasks) in a single command
- Success Criteria:
- Interactive mode: User controls progression with approval prompts at each phase
- Automatic mode: All phases execute without interruption when
--autoflag provided - All generated specs maintain quality comparable to manual workflow </background_information>
If --auto flag is present in $ARGUMENTS, you are in AUTOMATIC MODE.
In Automatic Mode:
- Execute ALL 4 phases in a continuous loop without stopping
- Use TodoWrite to track progress (4 tasks: init, requirements, design, tasks)
- Each phase completion updates TodoWrite and continues immediately
- IGNORE any "Next Step" messages from Phase 2-4 (they are for standalone usage)
- Stop ONLY after Phase 4 completes or if error occurs
Progress tracking with TodoWrite:
- Phase 1 complete = 1/4 tasks done → Continue to Phase 2
- Phase 2 complete = 2/4 tasks done → Continue to Phase 3
- Phase 3 complete = 3/4 tasks done → Continue to Phase 4
- Phase 4 complete = 4/4 tasks done → Output summary and exit
Core Task
Execute 4 spec phases sequentially. In automatic mode, execute all phases without stopping. In interactive mode, prompt user for approval between phases.
Execution Steps
Step 1: Parse Arguments and Initialize
Parse $ARGUMENTS:
- If contains
--auto: Automatic Mode (execute all 4 phases) - Otherwise: Interactive Mode (prompt at each phase)
- Extract description (remove
--autoflag if present)
Example:
"User profile with avatar upload --auto" → mode=automatic, description="User profile with avatar upload"
"User profile feature" → mode=interactive, description="User profile feature"
Create TodoWrite task list:
[
{"content": "Initialize spec", "activeForm": "Initializing spec", "status": "pending"},
{"content": "Generate requirements", "activeForm": "Generating requirements", "status": "pending"},
{"content": "Generate design", "activeForm": "Generating design", "status": "pending"},
{"content": "Generate tasks", "activeForm": "Generating tasks", "status": "pending"}
]
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.
- 3d ago First seen · 361 lines · 8 tokens per session scan A 10d0656982f2
spec-quick is a command published in the GitHub repository gotalab/cc-sdd (3,646 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 2,630 once invoked, about $0.0000 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
evaluate
Evaluate a skill across model tiers using blind testing.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
build
Run full verification pipeline.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
scenarios
The table of Gherkin scenarios the integration tests cover — so "what is actually tested?" is a question you can answer without running anything.