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-phase)<a href="https://agentmods.dev/commands/mrmyothet/zach-hair-studio/gsd-phase"><img src="https://agentmods.dev/badge/commands/mrmyothet/zach-hair-studio/gsd-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-phase"><img src="https://agentmods.dev/badge/commands/mrmyothet/zach-hair-studio/gsd-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.00021 | $0.00596 |
| Opus 5 | $0.00010 | $0.00298 |
| Sonnet 5 | $0.00004 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
gsd-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.
What it actually says
Mode routing:
- default (no flag): Add a new integer phase to the end of the current milestone → add-phase workflow
- --insert: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases → insert-phase workflow
- --remove: Remove a future phase and renumber subsequent phases → remove-phase workflow
- --edit: Edit any field of an existing phase in place → edit-phase workflow
| Flag | Action | Workflow |
|---|---|---|
| (none) | Add new integer phase at end of milestone | add-phase |
| --insert | Insert decimal phase (e.g., 72.1) after specified phase | insert-phase |
| --remove | Remove future phase, renumber subsequent | remove-phase |
| --edit | Edit fields of existing phase in place | edit-phase |
<execution_context> @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/workflows/add-phase.md @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/workflows/insert-phase.md @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/workflows/remove-phase.md @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/workflows/edit-phase.md </execution_context>
Parse the first token of $ARGUMENTS:
- If it is
--insert: strip the flag, pass remainder (format: ) to insert-phase workflow - If it is
--remove: strip the flag, pass remainder (phase number) to remove-phase workflow - If it is
--edit: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow - Otherwise: pass all of $ARGUMENTS (phase description) to add-phase workflow
Roadmap and state are resolved in-workflow via init phase-op and targeted reads.
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 · 57 lines · 21 tokens per session scan A 02b14abe71b8
gsd-phase is a command published in the GitHub repository mrmyothet/zach-hair-studio (11 stars, last pushed 28d ago), licensed MIT. It adds 21 tokens to every session and 596 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.