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/validategit 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.00016 | $0.01651 |
| Opus 5 | $0.00008 | $0.00826 |
| Sonnet 5 | $0.00003 | $0.00330 |
| Haiku 4.5 | $0.00002 | $0.00165 |
Grade A, and why
validate 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate — Plan Verification
Checks that the implementation actually meets the plan's success criteria. Run after /implement finishes, or as a re-check on an already-archived plan.
This is verification, not review. You are checking whether specific, stated criteria are met — not forming new opinions about quality.
When to skip. New plans authored with a
verification.jsonlalready had every row flipped at/implement's Phase-End Verification Gate./validatehere is for:
- Legacy plans with markdown criteria only (no
verification.jsonl).- Re-runs of an already-archived plan against its current
verification.jsonlstate.- Sanity passes when a deliverable was edited after
/implementcompleted.
Step 1: Detect the Plan
Resolve the plan path:
- If passed as the command argument, use it.
- Otherwise, the most recent plan under
plans/active/(highest date). - Read the full Success Criteria checklist from the plan.
If no plan exists: stop and say "No plan found. Run /plan first."
If the plan has no success criteria: stop and say "Plan has no success criteria. Add them to the plan before validating."
Step 2: Mechanical Verification Pass (when verification.jsonl exists)
Plans created with the verification spine carry a per-plan verification.jsonl with one row per atomic Success Criterion. When that file exists, the runner is canonical — prose judgment in Step 3 is replaced by the runner's flip log.
PLAN_DIR="$(dirname "$PLAN_PATH")"
if [[ -f "$PLAN_DIR/verification.jsonl" ]]; then
bash "${CLAUDE_PLUGIN_ROOT}/scripts/verification-run.sh" "$PLAN_DIR"
RUN_RC=$?
fi
Behavior:
- Walks the latest-wins state of every row, runs each
passes:falserow'scheck_command, captures combined output to<plan-dir>/evidence/<id>.log, and flips the row viaverification-flip.sh. - Distinguishes
command not found(rc=127) from real check failures in stderr; both flip the row topasses:false-with-evidence so the audit trail records the failure mode. - Final summary line:
verification: N/M verified, K failed, L skipped (phase=<filter>). - Idempotent — already-passing rows are reported but not re-executed.
- Optional
--phase=<phase-slug>flag scopes the run to a single phase.
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 · 166 lines · 16 tokens per session scan A d34969193c86
validate is a command published in the GitHub repository keez97/phase-gate (1 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,651 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.