Borrowing it
Nothing to install: this file belongs to adawalli/nexus. 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/adawalli/nexus/main/.claude/commands/agent-os/shape-spec.mdgit clone --depth 1 https://github.com/adawalli/nexusWrote 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/adawalli/nexus/shape-spec)<a href="https://agentmods.dev/commands/adawalli/nexus/shape-spec"><img src="https://agentmods.dev/badge/commands/adawalli/nexus/shape-spec/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/adawalli/nexus/shape-spec"><img src="https://agentmods.dev/badge/commands/adawalli/nexus/shape-spec.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.00000 | $0.00423 |
| Opus 5.5 | $0.00000 | $0.00169 |
| Sonnet 5.5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
shape-spec 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 2mo 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
Spec Shaping Process
You are helping me shape and plan the scope for a new feature. The following process is aimed at documenting our key decisions regarding scope, design and architecture approach. We will use our findings from this process later when we write the formal spec document (but we are NOT writing the formal spec yet).
This process will follow 3 main phases, each with their own workflow steps:
Process overview (details to follow)
PHASE 1. Initilize spec PHASE 2. Research requirements for this spec PHASE 3. Inform the user that the spec has been initialized
Follow each of these phases and their individual workflows IN SEQUENCE:
Multi-Phase Process:
PHASE 1: Initialize Spec
Use the spec-initializer subagent to initialize a new spec.
IF the user has provided a description, provide that to the spec-initializer.
The spec-initializer will provide the path to the dated spec folder (YYYY-MM-DD-spec-name) they've created.
PHASE 2: Research Requirements
After spec-initializer completes, immediately use the spec-shaper subagent:
Provide the spec-shaper with:
- The spec folder path from spec-initializer
The spec-shaper will give you several separate responses that you MUST show to the user. These include:
- Numbered clarifying questions along with a request for visual assets (show these to user, wait for user's response)
- Follow-up questions if needed (based on user's answers and provided visuals)
IMPORTANT:
- Display these questions to the user and wait for their response
- The spec-shaper may ask you to relay follow-up questions that you must present to user
PHASE 3: Inform the user
After all steps complete, inform the user:
Spec shaping is complete!
✅ Spec folder created: `[spec-path]`
✅ Requirements gathered
✅ Visual assets: [Found X files / No files provided]
NEXT STEP 👉 Run `/write-spec` to generate the detailed specification document.
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.
- 2mo ago First seen · 56 lines · 0 tokens per session scan A 818c44ceeff3
shape-spec is a command published in the GitHub repository adawalli/nexus (21 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 423 tokens. 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.
shape-spec compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| shape-specadawalli/nexus | Command | 21 | 16d ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |