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-teamnpx skills add alonf/specrew --skill specrew-teamgit 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-team)<a href="https://agentmods.dev/skills/alonf/specrew/specrew-team"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-team.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 | $0.00019 | $0.00712 |
| Opus 5 | $0.00010 | $0.00356 |
| Sonnet 5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
specrew-team 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specrew-team
Type: Operational Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-team
Purpose
Manage Squad team members and baseline-role composition in the current Specrew project.
When to Use
- When adding, listing, updating, or removing Squad team members.
- When managing the team composition for a project.
- Invoke this skill when the user says: "Show team members", "Add a team member", "List the Squad team", "Manage the team".
Boundary Safety
This skill manages team configuration only. It does not authorize or imply approval to advance any lifecycle boundary. Managed baseline roles (Spec Steward, Planner, Implementer, Reviewer, Retro Facilitator) are preserved according to the baseline-role rules.
Coexistence Contract
This skill is part of the /specrew-* command surface and does not collide with /speckit.* commands.
Invocation
/specrew-team list [--project-path <path>]
/specrew-team add <member-name> --role <role> --charter <text> [--project-path <path>]
/specrew-team update <member-name> [--role <role>] [--charter <text>] [--project-path <path>]
/specrew-team remove <member-name> [--project-path <path>]
Backed by: specrew team / scripts/specrew-team.ps1
Inputs
Subcommands
| Subcommand | Description |
|---|---|
list |
Show current team members and their roles |
add <member-name> |
Add a new team member |
update <member-name> |
Update an existing team member's role or charter |
remove <member-name> |
Remove a non-baseline team member |
Common Options
| Input | Type | Required | Description |
|---|---|---|---|
--project-path |
string | No | Target Specrew project path (defaults to current directory) |
add / update Options
| Input | Type | Required | Description |
|---|---|---|---|
--role |
string | Required for add | Human-readable role name |
--charter |
string | Required for add | Charter text describing the role's responsibilities |
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.
- 4d ago First seen · 89 lines · 19 tokens per session scan A c5684cbe454d
specrew-team is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 712 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…