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.
git clone --depth 1 https://github.com/mrmyothet/zach-hair-studioWrote 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/mrmyothet/zach-hair-studio/gsd-spec-phase)<a href="https://agentmods.dev/commands/mrmyothet/zach-hair-studio/gsd-spec-phase"><img src="https://agentmods.dev/badge/commands/mrmyothet/zach-hair-studio/gsd-spec-phase/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/mrmyothet/zach-hair-studio/gsd-spec-phase"><img src="https://agentmods.dev/badge/commands/mrmyothet/zach-hair-studio/gsd-spec-phase.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.00023 | $0.00605 |
| Opus 5 | $0.00012 | $0.00302 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
gsd-spec-phase 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 9d 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
1 near-identical copy found in the catalogue:
- gsd:spec-phase — 89% identical, 8 lines differ
What it actually says
Position in workflow: spec-phase → discuss-phase → plan-phase → execute-phase → verify
How it works:
- Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
- Scout the codebase — understand current state before asking questions
- Run Socratic interview loop (up to 6 rounds, rotating perspectives)
- Score ambiguity across 4 weighted dimensions after each round
- Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
- Commit SPEC.md — discuss-phase picks it up automatically on next run
Output: {phase_dir}/{padded_phase}-SPEC.md — falsifiable requirements that lock "what/why" before discuss-phase handles "how"
<execution_context> @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/workflows/spec-phase.md @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/templates/spec.md </execution_context>
<runtime_note>
Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent.
</runtime_note>
Flags:
--auto— Skip interactive questions; Claude selects recommended defaults and writes SPEC.md--text— Use plain-text numbered lists instead of TUI menus (required for/rcremote sessions)
Context files are resolved in-workflow using init phase-op.
MANDATORY: Read the workflow file BEFORE taking any action. The workflow contains the complete step-by-step process including the Socratic interview loop, ambiguity scoring gate, and SPEC.md generation. Do not improvise from the objective summary above.
<success_criteria>
- Codebase scouted for current state before questioning begins
- All 4 ambiguity dimensions scored after each interview round
- Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met
- SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria
- SPEC.md committed atomically
- User knows they can now run /gsd-discuss-phase which will load SPEC.md automatically </success_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.
- 9d ago First seen · 64 lines · 23 tokens per session scan A 42bec05e62f7
gsd-spec-phase is a command published in the GitHub repository mrmyothet/zach-hair-studio (11 stars, last pushed 28d ago), licensed MIT. It adds 23 tokens to every session and 605 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.