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 skills/arittr/spectacular/using-spectacularnpx skills add arittr/spectacular --skill using-spectaculargit clone --depth 1 https://github.com/arittr/spectacularWrote 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/arittr/spectacular/using-spectacular)<a href="https://agentmods.dev/skills/arittr/spectacular/using-spectacular"><img src="https://agentmods.dev/badge/skills/arittr/spectacular/using-spectacular.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 | $0.00041 | $0.01034 |
| Opus 5 | $0.00020 | $0.00517 |
| Sonnet 5 | $0.00008 | $0.00207 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
using-spectacular 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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<EXTREMELY_IMPORTANT> You have spectacular.
The content below is your introduction to using spectacular:
Using Spectacular
Spectacular extends superpowers with spec-anchored development workflows. Before responding to user requests for features or refactors, you MUST check if spectacular workflows apply.
MANDATORY FIRST RESPONSE PROTOCOL
Before responding to ANY user message about features, refactors, or implementations:
- ☐ Does request involve implementing/refactoring features?
- ☐ Is there a
docs/constitutions/current/directory in this project? - ☐ If yes → Use spectacular workflow (spec → plan → execute)
- ☐ If no constitution → Ask if user wants to use spectacular
Responding to feature requests WITHOUT this check = automatic failure.
Core Spectacular Workflow
User request → /spectacular:spec → /spectacular:plan → /spectacular:execute
Each command has a specific purpose:
-
/spectacular:spec- Generate feature specification- When: User describes a feature to implement or refactor
- Output:
specs/{runId}-{feature-slug}/spec.md - Includes: Requirements, architecture, acceptance criteria
- References: Constitution rules (doesn't duplicate them)
-
/spectacular:plan- Decompose spec into execution plan- When: After spec is reviewed and approved
- Input: Path to spec.md
- Output:
specs/{runId}-{feature-slug}/plan.md - Analyzes: Task dependencies, file overlaps
- Generates: Sequential/parallel phases with time estimates
-
/spectacular:execute- Execute plan with parallel orchestration- When: After plan is reviewed and approved
- Input: Path to plan.md
- Creates: Worktrees, spawns subagents, stacks branches
- Quality gates: Tests/lint after each task, code review after each phase
Constitutions: Architectural Truth
If docs/constitutions/current/ exists, it contains immutable architectural rules:
- architecture.md - Layer boundaries, project structure
- patterns.md - Mandatory patterns (e.g., "use Zod for validation")
- tech-stack.md - Approved libraries and versions
- testing.md - Testing requirements
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.
- 5d ago First seen · 113 lines · 41 tokens per session scan A cab7ebf18b11
using-spectacular is a skill published in the GitHub repository arittr/spectacular (20 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 1,034 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…