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 specrew-versiongit 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/specrew-version)<a href="https://agentmods.dev/skills/alonf/specrew/specrew-version"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-version/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/specrew-version"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-version.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.00017 | $0.00717 |
| Opus 5.5 | $0.00007 | $0.00287 |
| Sonnet 5.5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
specrew-version 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specrew-version
Type: Informational Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-version
Purpose
Show the installed Specrew version and slash-command compatibility state. Reports both the installed/runtime version and the project baseline version from .specrew/config.yml.
When to Use
- When a contributor wants to know which version of Specrew is installed.
- When checking whether the slash-command surface is compatible with the current baseline.
- When diagnosing compatibility issues before or after
specrew update. - Invoke this skill when the user says: "What version of Specrew is installed?", "Show Specrew version", "Is the slash-command surface compatible?", "Check Specrew version".
Boundary Safety
This skill provides version and compatibility information only. It does not authorize or imply approval to advance any lifecycle boundary.
Invocation
/specrew-version [--project-path <path>]
Backed by: specrew version / scripts/specrew-version.ps1
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
--project-path |
string | No | Target Specrew project path (defaults to current directory) |
Outputs
- Installed Specrew version (from module or
Specrew.psd1) - Project baseline version (from
.specrew/config.yml) - Slash-command compatibility state:
compatible— the installed version can service the project baseline recorded in.specrew/config.ymlincompatible— the installed version is older than the project baseline; upgrade guidance is shownunknown— the installed version cannot be determined
- Remediation guidance when compatibility is not met:
- For outdated installed version:
Update-Module Specrewor equivalent - For a matching development tree: set
SPECREW_MODULE_PATH - For outdated project baseline:
specrew update
- For outdated installed version:
Argument Whitelist
Only --project-path is accepted in v1. Unknown arguments are rejected with explicit help guidance.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 81 lines · 17 tokens per session scan A 01960324a63a
specrew-version is a skill published in the GitHub repository alonf/specrew (55 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 717 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…