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 commands/geoloeg-ist/agents-reverse-engineer/plan-phasegit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWrote 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/geoloeg-ist/agents-reverse-engineer/plan-phase)<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/plan-phase"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/plan-phase.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.00020 | $0.03614 |
| Opus 5 | $0.00010 | $0.01807 |
| Sonnet 5 | $0.00004 | $0.00723 |
| Haiku 4.5 | $0.00002 | $0.00361 |
Grade A, and why
gsd:plan-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 3d 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 — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<execution_context> @./.claude/get-shit-done/references/ui-brand.md </execution_context>
Default flow: Research (if needed) → Plan → Verify → Done
Orchestrator role: Parse arguments, validate phase, research domain (unless skipped or exists), spawn gsd-planner agent, verify plans with gsd-plan-checker, iterate until plans pass or max iterations reached, present results.
Why subagents: Research and planning burn context fast. Verification uses fresh context. User sees the flow between agents in main context.
Flags:
--research— Force re-research even if RESEARCH.md exists--skip-research— Skip research entirely, go straight to planning--gaps— Gap closure mode (reads VERIFICATION.md, skips research)--skip-verify— Skip planner → checker verification loop
Normalize phase input in step 2 before any directory lookups.
1. Validate Environment and Resolve Model Profile
ls .planning/ 2>/dev/null
If not found: Error - user should run /gsd:new-project first.
Resolve model profile for agent spawning:
MODEL_PROFILE=$(cat .planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")
Default to "balanced" if not set.
Model lookup table:
| Agent | quality | balanced | budget |
|---|---|---|---|
| gsd-phase-researcher | opus | sonnet | haiku |
| gsd-planner | opus | opus | sonnet |
| gsd-plan-checker | sonnet | sonnet | haiku |
Store resolved models for use in Task calls below.
2. Parse and Normalize Arguments
Extract from $ARGUMENTS:
- Phase number (integer or decimal like
2.1) --researchflag to force re-research--skip-researchflag to skip research--gapsflag for gap closure mode--skip-verifyflag to bypass verification loop
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.
- 3d ago First seen · 526 lines · 20 tokens per session scan A 2f723ef786bf
gsd:plan-phase is a command published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 27d ago), licensed MIT. It adds 20 tokens to every session and 3,614 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-08-30.
Other commands, from other repositories
auto-reason
Subjective self-refinement with blind judging, Borda aggregation, and provider-agnostic model routing.
deep-research
Deep research — produce a cited decision-grade research report and artifact bundle.
goals
Goal-oriented mission entrypoint — set, view, or drive long-running objectives through the mission system.
launch-worker
Manually launch headless workers against one or more GitHub issues.
check-routines
Check and safely repair aidevops routine scheduler health.
local-permissions-check
Audit local host/runtime permissions for aidevops on macOS, Linux, Windows, and WSL.