Borrowing it
Nothing to install: this file belongs to alonf/specrew. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alonf/specrew/main/.squad/skills/phase2-approval-helper-validation/SKILL.mdgit 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/phase2-approval-helper-validation)<a href="https://agentmods.dev/skills/alonf/specrew/phase2-approval-helper-validation"><img src="https://agentmods.dev/badge/skills/alonf/specrew/phase2-approval-helper-validation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00218 |
| Opus 5 | $0.00000 | $0.00109 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
phase2-approval-helper-validation 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 4d 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
phase2-approval-helper-validation
Purpose
Add shared governance parsing helpers without coupling later validator work to ad hoc Markdown or approval parsing.
When to Use
- A Phase 2 governance slice adds helpers for
hardening-gate.md, routing evidence, or approval references. - The helper layer should be validated before policy-enforcement work lands.
- You need one proof path that distinguishes approved deferrals from still-blocking unresolved concerns.
Pattern
- Centralize Markdown metadata/table parsing in the shared governance helper rather than re-implementing it inside each caller.
- Add approval-reference resolution that can map canonical
.squad\decisions.mdentries back to human approval evidence. - Parse routing evidence into structured requested/effective class fields so later enforcement can stay policy-focused.
- Validate the helper layer with an integration scenario that includes both a human-approved deferral and a separate blocking
tbdconcern. - Keep lifecycle bookkeeping truthful: mark only the helper task complete and advance the next ready task window without implying later enforcement work already landed.
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.
- 4d ago First seen · 20 lines · 0 tokens per session scan A 10fa88cc3bad
phase2-approval-helper-validation is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 218 tokens. 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.