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 skills/firatcand/forge/phase-gatenpx skills add firatcand/forge --skill phase-gategit clone --depth 1 https://github.com/firatcand/forgeWhat 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.00036 | $0.00331 |
| Opus 5 | $0.00018 | $0.00166 |
| Sonnet 5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
phase-gate 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.
What it actually says
/phase-gate
Delegate to phase-gatekeeper.
Args
phase-{N}(e.g.,phase-1)
Steps
- Read
plans/phases.yamlforphase-N.gate_criteria - Verify all phase-N tasks are Done in Linear (abort with list if not)
- Run
gate_check_commandfrom phases.yaml (e.g.,npm run e2e && npm run typecheck) - Generate
docs/retros/phase-{N}.md:- Tasks shipped (with PR links)
- Decisions made
- Scope changes from original phases.yaml
- Learnings to harvest
- What to do differently in phase-{N+1}
- Print summary, ask: "Approve advancing to phase-{N+1}? [y/N]"
- On
y:- Linear: close Cycle N, activate Cycle N+1
- Move all phase-(N+1) tasks Backlog → Todo
- Update phases.yaml:
phase-N.status = "complete" - Commit retro
- On
N: list what's missing, exit (no partial advances)
Output
If approved: confirmation + Phase N+1 task summary. If not: list of blockers.
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 · 38 lines · 36 tokens per session scan A 66fc298ea594
phase-gate is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 331 once invoked, about $0.0002 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 skills, from other repositories
ospec-goal
Create or advance a full OSpec goal using the current document, task graph, worker, review, and evidence workflow.
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
prospec-verify
Verify Implementation - Run 5+1 dimension audit (tasks, spec compliance, constitution, knowledge-implementation consistency, tests, design consistency) and assign quality grade (S/A/B/C/D). Triggers: verify, audit, quality check, 驗證, 稽核, 品質檢查, 評級.
prospec-archive
Archive Changes - Archive completed changes, generate summary, sync requirements to feature specs, and gate archiving on Knowledge sync. Triggers: archive, spec sync, finalize change, 封存, 歸檔, 收尾, 規格同步.
prospec-knowledge-generate
Generate AI Knowledge - Read raw-scan.md, analyze project structure, autonomously decide module boundaries, and produce Recipe-First module READMEs and index. Triggers: generate knowledge, analyze project, module split, 產生知識, 知識庫, 分析專案, 模組拆分.