Borrowing it
Nothing to install: this file belongs to jumppad-labs/spektacular. 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/jumppad-labs/spektacular/main/.claude/skills/spek-design/SKILL.mdgit clone --depth 1 https://github.com/jumppad-labs/spektacularWrote 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/skills/jumppad-labs/spektacular/spek-design)<a href="https://agentmods.dev/skills/jumppad-labs/spektacular/spek-design"><img src="https://agentmods.dev/badge/skills/jumppad-labs/spektacular/spek-design/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/skills/jumppad-labs/spektacular/spek-design"><img src="https://agentmods.dev/badge/skills/jumppad-labs/spektacular/spek-design.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.00016 | $0.02191 |
| Opus 5.5 | $0.00006 | $0.00876 |
| Sonnet 5.5 | $0.00003 | $0.00438 |
| Haiku 4.5 | $0.00002 | $0.00219 |
Grade A, and why
spek-design 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version check first. Before running any other command, run
go run . version check.
- On
status: "match", continue with the skill and produce no version-related output.- On
"mismatch","missing"or"upgrade_needed", the project's settings or installed Spektacular files are out of date: relay the response'sactionmessage to the user, ask them to rungo run . migrate(they can preview it withgo run . migrate --dry-run), and wait for their decision before continuing.- On
"unsupported_format", relay theactionmessage: the project was written by a newer Spektacular, which the user must install before continuing.- Never run
migrateorinit, and never modify installed files yourself. Upgrading is always an explicit, user-initiated action.
What this skill does
This skill handles the four ways a design document enters a project: helping the user work one
out that does not exist yet, bringing in one they already have, revising one that exists, and
recording a reference to one already stored. Unlike spek-new, spek-plan and spek-implement,
it does not drive an interactive CLI state machine — it is a static playbook. That is deliberate
and load-bearing: a state machine could not run inside a spec workflow, and design conversation
happens during one. The agent recognises which situation the user is in, picks one of four
branches, and calls the matching go run . design command directly.
Two classes of design document exist and the difference matters at every branch. A design the project already had is stored exactly as supplied and never gains anything. A design Spektacular authors with the user carries the same lifecycle record every spec and plan carries, so it reports where it stands, which spec's conversation produced it, and which specs reference it.
When to invoke
Invoke this skill whenever a design document is in play. Typical natural-language triggers:
- "Help me write this up as a design." / "Can you turn this into a design document?"
- "I already have a design for this, can you store it?" / "Here is our API design doc."
- "That design has changed." / "Update the retry design to cover timeouts."
- "Point this spec at the design we already have."
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 · 167 lines · 16 tokens per session scan A 99a6444f6774
spek-design is a skill published in the GitHub repository jumppad-labs/spektacular (20 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 2,191 once invoked, about $0.0001 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-09-22.
Other skills, from other repositories
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…