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/keez97/phase-gate/implementgit clone --depth 1 https://github.com/keez97/phase-gateWhat 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.00028 | $0.03325 |
| Opus 5 | $0.00014 | $0.01663 |
| Sonnet 5 | $0.00006 | $0.00665 |
| Haiku 4.5 | $0.00003 | $0.00332 |
Grade A, and why
implement 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 yesterday.
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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/implement — Execution Phase
Walks a plan from plans/active/ phase by phase. For each phase: optionally delegate to the implementer agent against the phase's file manifest; run the phase-end verification gate; on green, advance. On red, surface failures and stop.
Preflight 1: Plan Manifest Check
Before any phase-level work:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-plan-manifest.sh" "$PLAN_PATH"
- Exit 0 → proceed.
- Exit 1 → STOP. The script prints per-phase violations to stderr. Surface them to the user and ask whether to (a) amend the plan to add missing
#### Filesblocks, or (b) mark the affected phasesinline-onlyin their headings and re-run preflight. Do not proceed until it exits 0.
Rationale: the implementer agent delegation flow requires each phase's scope to be enumerable. A phase without a manifest is not safely delegable.
Preflight 2: Verification Manifest Check
If the plan has a verification.jsonl, every row's check_command must be filled in before implementation begins:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-verification-manifest.sh" "$PLAN_DIR"
- Exit 0 → proceed (includes the opt-out case: no
verification.jsonlpresent). - Exit 1 → STOP. Script prints each stub row's id + criterion to stderr. Ask the user whether to (a) fill the
check_commandfields inverification.jsonl(Edit tool — bounded authoring exception percommands/plan.mdStep 2.7), or (b) delete the stub rows if the criterion is being dropped. Re-run preflight until it exits 0.
Rationale: rows may start as stubs at /plan time but /implement requires every verification claim to be mechanically checkable. A null check_command is not a gate — it is a todo masquerading as one.
Session Start
Read the plan fully. Check existing checkmarks (- [x]) on phase tasks — phases already done don't get re-run. Verify all dependencies in the plan exist (files, scripts, env vars). Resolve all Open Questions or stop and flag them to the user.
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.
- yesterday First seen · 235 lines · 28 tokens per session scan A 8e153d6c6b5d
implement is a command published in the GitHub repository keez97/phase-gate (1 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 3,325 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-31.
Other commands, from other repositories
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
toh-help
Display all Toh Framework commands and quick usage guide.
feature
Create a feature specification using spec-driven development.
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
deep-audit.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Ornek cikti.