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 agentmods add skills/alonf/specrew/specrew-updatenpx skills add alonf/specrew --skill specrew-updategit clone --depth 1 https://github.com/alonf/specrewWhat 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 | $0.00019 | $0.00841 |
| Opus 5 | $0.00010 | $0.00420 |
| Sonnet 5 | $0.00004 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
specrew-update 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 2d 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-update
Type: Operational Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-update
Purpose
Refresh Specrew-managed assets and supported platform baselines (Spec Kit, Squad) in the current project.
When to Use
- When a contributor wants to update Specrew assets in an existing project.
- When refreshing the slash-command surface after a new Specrew release.
- When synchronizing Spec Kit or Squad extensions to a newer version.
- Invoke this skill when the user says: "Update Specrew", "Refresh Specrew assets", "Update Spec Kit", "Update Squad".
Boundary Safety
This skill updates distribution-managed assets only. It does not authorize or imply approval to advance any lifecycle boundary. The scope of updates is bounded by the documented argument whitelist — no undocumented expansion occurs.
Coexistence Contract
This skill is additive. Refreshing Specrew assets does not remove or shadow /speckit.* command surfaces.
Invocation
/specrew-update [--project-path <path>] [--info] [--all]
[--specrew] [--squad] [--spec-kit] [--skip-update-check]
[--upstream-latest]
Backed by: specrew update / scripts/specrew-update.ps1
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
--project-path |
string | No | Target Specrew project path (defaults to current directory) |
--info |
flag | No | Show version and update information without performing updates |
--all |
flag | No | Update all managed components (Specrew, Spec Kit, Squad) |
--specrew |
flag | No | Update Specrew-managed assets only |
--squad |
flag | No | Update Squad-managed assets only |
--spec-kit |
flag | No | Update Spec Kit extension only |
--skip-update-check |
flag | No | Skip the PSGallery version-available check |
--upstream-latest |
flag | No | Target upstream-latest versions instead of Specrew-validated max_tested (use with care; see Outputs) |
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.
- 2d ago First seen · 81 lines · 19 tokens per session scan A e388b9b66e22
specrew-update is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 841 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-08-30.
Other skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.