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 skills add firatcand/forge --skill phase-gategit clone --depth 1 https://github.com/firatcand/forgeWrote 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/skills/firatcand/forge/phase-gate)<a href="https://agentmods.dev/skills/firatcand/forge/phase-gate"><img src="https://agentmods.dev/badge/skills/firatcand/forge/phase-gate/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/skills/firatcand/forge/phase-gate"><img src="https://agentmods.dev/badge/skills/firatcand/forge/phase-gate.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.00036 | $0.00331 |
| Opus 5.5 | $0.00014 | $0.00132 |
| Sonnet 5.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 1mo 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.
- 1mo 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 2mo ago), licensed MIT. It adds 36 tokens to every session and 331 once invoked, about $0.0001 per session on Opus 5.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
github-triage
Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from git remote; all GitHub calls go through gh.
to-issues
Decompose a plan, PRD, or spec into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.
loop-build
(loop-engineering) Implements exactly one feature from the BACKLOG.md Backlog — syncs main, acquires the loop lock, creates a feature branch, implements all acceptance criteria with tests, visually inspects UI changes, passes the independent verifier, and opens a PR. Use for Build-mode loop runs, or when asked to…
loop-report
(loop-engineering) Runs the daily Report-mode triage — checks open PRs, CI status and the BACKLOG.md backlog, then updates STATE.md and appends to the run log without writing any code. Use for scheduled daily loop runs, project health checks, or when asked to "triage", "run report mode", or "update the loop state".
to-issues
Decompose a plan, PRD, or spec into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.
github-triage
Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from git remote; all GitHub calls go through gh.