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 powershell-cli-contract-reviewgit 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/powershell-cli-contract-review)<a href="https://agentmods.dev/skills/alonf/specrew/powershell-cli-contract-review"><img src="https://agentmods.dev/badge/skills/alonf/specrew/powershell-cli-contract-review.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.00020 | $0.00684 |
| Opus 5 | $0.00010 | $0.00342 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
powershell-cli-contract-review 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Use this when reviewing a standalone PowerShell script that is presented as a contract-facing CLI. These reviews fail easily when the implementation only works via PowerShell-native switches while the documented --flag surface, prompt wording, or required probes are unverified.
Patterns
- Validate the exact documented invocation first (for example
.\script.ps1 --dry-run) before accepting equivalent PowerShell-native forms such as-DryRun. - For advanced scripts that support GNU-style flags, set
CmdletBinding(PositionalBinding = $false)and parseValueFromRemainingArgumentsexplicitly so--flagtokens cannot misbind into typed positional parameters. - Capture a live interactive transcript and compare it to the contract fields, not just to the existence of
Read-Host. - Prove GNU-style
--flagsupport through the exact live script surface (& .\script.ps1 --flag ...from PowerShell), not only through nested harnesses or equivalent helper wrappers. Those wrappers can mask that the advertised surface still ignores--*arguments. - Search the implementation for each required external probe/API call; a missing mandated probe is a material gap even if adjacent probes succeed.
- Separate graceful degradation from completeness: a fallback path can be correct while the overall slice still fails for missing contract behavior.
- Confirm banned concerns (billing, cost, routing) are absent with direct code search instead of inference.
Examples
scripts\specrew-init.ps1accepted-DryRunbut--dry-runmisbound asSpecKitVersion; that is a contract failure on the advertised standalone surface.scripts\specrew-init.ps1needed bothPositionalBinding = $falseand explicitCliArgsparsing so--dry-run --project-path <dir>worked on the advertised standalone surface without breaking PowerShell-native switches.- A re-review must re-run the exact contract surface after a parser fix; in this repo, code that looked correct still left
& .\scripts\specrew-init.ps1 --dry-run --force --project-path <dir>prompting interactively and targeting the current directory. - The FR-022 consent prompt showed agent name plus access path, but omitted availability even though availability was required in the prompt contract.
- A delegated-agent probe based on
copilot help configdegraded correctly when unavailable, but the missinggh api /userprobe still blocked acceptance.
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 · 39 lines · 20 tokens per session scan A 40a51f924ffe
powershell-cli-contract-review is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 684 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
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.