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-plan-review-convergence)<a href="https://agentmods.dev/commands/mrmyothet/zach-hair-studio/gsd-plan-review-convergence"><img src="https://agentmods.dev/badge/commands/mrmyothet/zach-hair-studio/gsd-plan-review-convergence/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-plan-review-convergence"><img src="https://agentmods.dev/badge/commands/mrmyothet/zach-hair-studio/gsd-plan-review-convergence.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.00934 |
| Opus 5 | $0.00010 | $0.00467 |
| Sonnet 5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
gsd-plan-review-convergence 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
Flow: Skill("gsd-plan-phase") → Agent→Skill("gsd-review") → check unresolved HIGH + actionable non-HIGH → Skill("gsd-plan-phase --reviews") → Agent→Skill("gsd-review") → ... → Converge or escalate
Replaces gsd-plan-phase's internal gsd-plan-checker with external AI reviewers (codex, gemini, etc.). Plan-phase runs inline (bare Skill at depth 0) so it can spawn gsd-planner/gsd-plan-checker at depth 1. Review runs inside an isolated Agent (gsd-review is a Bash leaf — no sub-agents needed). Orchestrator only does loop control.
Orchestrator role: Parse arguments, validate phase, run plan-phase inline (Skill at depth 0), spawn an Agent for gsd-review, check unresolved HIGH and actionable non-HIGH counts, stall detection, escalation gate.
<execution_context> @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/workflows/plan-review-convergence.md @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/references/revision-loop.md @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/references/gates.md @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/references/agent-contracts.md </execution_context>
<runtime_note>
Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API. Do not skip questioning steps because AskUserQuestion appears unavailable; use vscode_askquestions instead.
</runtime_note>
Flags:
--codex— Use Codex CLI as reviewer (default if no reviewer specified)--gemini— Use Gemini CLI as reviewer--claude— Use Claude CLI as reviewer (separate session)--opencode— Use OpenCode as reviewer--ollama— Use local Ollama server as reviewer (OpenAI-compatible, default hosthttp://localhost:11434; configure model viareview.models.ollama)--lm-studio— Use local LM Studio server as reviewer (OpenAI-compatible, default hosthttp://localhost:1234; configure model viareview.models.lm_studio)--llama-cpp— Use local llama.cpp server as reviewer (OpenAI-compatible, default hosthttp://localhost:8080; configure model viareview.models.llama_cpp)--all— Use all available CLIs and running local model servers--max-cycles N— Maximum replan→review cycles (default: 3)
Feature gate: This command requires workflow.plan_review_convergence=true. Enable with:
gsd config-set workflow.plan_review_convergence true
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 · 61 lines · 21 tokens per session scan A 15fdeb1413bd
gsd-plan-review-convergence 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 934 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.