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 alonf/specrew --skill phase-gate-boundary-syncgit clone --depth 1 https://github.com/alonf/specrewWrote 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/alonf/specrew/phase-gate-boundary-sync)<a href="https://agentmods.dev/skills/alonf/specrew/phase-gate-boundary-sync"><img src="https://agentmods.dev/badge/skills/alonf/specrew/phase-gate-boundary-sync.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.1 | $0.00028 | $0.00254 |
| Opus 5 | $0.00014 | $0.00127 |
| Sonnet 5 | $0.00006 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
phase-gate-boundary-sync 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-boundary-sync
Purpose
Prevent lifecycle drift when a requirement from a later delivery phase becomes the current iteration's actual go/no-go gate.
When to Use
- A slice introduces a new pre-implementation or pre-review gate.
- Planning guidance, implementation readiness guidance, and coordinator policy can each misstate whether that gate is already active.
- The current work should tighten lifecycle language without falsely claiming later automation or enforcement already exists.
Pattern
- Update the planning checkpoint to describe the gate as required future readiness, not as already satisfied evidence.
- Update the implementation checkpoint to name the concrete artifact, required sign-off fields, and any human-only deferral rule.
- Update the coordinator policy so handoffs and readiness summaries carry the same boundary language.
- Keep adjacent later-phase capabilities explicitly deferred unless the active slice truly delivers them.
- Repair iteration state/plan/drift artifacts immediately after the guidance lands so execution truth matches the newly accepted gate language.
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 · 28 lines · 28 tokens per session scan A 10ff2c13aae2
phase-gate-boundary-sync is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 254 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.