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 hardening-gate-fixturesgit 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/hardening-gate-fixtures)<a href="https://agentmods.dev/skills/alonf/specrew/hardening-gate-fixtures"><img src="https://agentmods.dev/badge/skills/alonf/specrew/hardening-gate-fixtures/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/alonf/specrew/hardening-gate-fixtures"><img src="https://agentmods.dev/badge/skills/alonf/specrew/hardening-gate-fixtures.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00258 |
| Opus 5 | $0.00014 | $0.00129 |
| Sonnet 5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
hardening-gate-fixtures 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 9d 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
Context
Use this when Phase 2 fixture work needs deterministic hardening-gate scenarios before the final validator or orchestration path is fully implemented.
Patterns
- Mirror the shipped hardening-gate schema exactly: metadata block plus
## Concern Reviewtable. - Cover all required concern families in each scenario, not just the one that changes the verdict.
- For
blocked, keep at least one blocking concern attbd. - For
approved-deferral, add a canonical.squad\decisions.mdentry with the same approval reference cited in the artifact. - For
ready, keep every blocking concernaddressedor truthfullynot-applicable. - Update iteration lifecycle artifacts in the same change so fixture delivery status stays truthful.
Anti-Patterns
- Creating an
approved-deferralfixture without human approval evidence. - Omitting concern rows and assuming later tests will infer them.
- Advancing later User Story 2 tasks while fixture-only work is still the active scope.
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.
- 9d ago First seen · 27 lines · 27 tokens per session scan A c38ab51f946b
hardening-gate-fixtures is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 258 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
ag-pipeline-issue
Pipeline Issue→SPEC→Build→Verify→Test. Toda GitHub Issue gera SPEC antes de implementar, e toda implementacao e verificada contra a SPEC e testada. Use when starting work on a GitHub Issue.
ds-build
Plan executor — take an issue, a specs/{feature}/tasks.md, or a plain request and implement it unit by unit with a verify signal per unit, red-proven tests, budgeted backtracking, and a code-proven close. Use when the plan exists and the work is to be done, not planned.
scaffold
Scaffold a new feature end-to-end in one pass — module, types, tests stub, docs stub, and registration — so the first commit isn't boilerplate drift. Automation-first; infers the project's conventions from neighbors. Use whenever the user wants to scaffold a feature, stub a module, or runs /scaffold, or before…
project-setup
Bootstrap new projects with strong typing, linting, formatting, and testing. Supports Python, TypeScript, and other languages with research fallback.
bmad-agent-dev
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…