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-wherenpx skills add alonf/specrew --skill specrew-wheregit 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-where)<a href="https://agentmods.dev/skills/alonf/specrew/specrew-where"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-where.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.00020 | $0.00788 |
| Opus 5 | $0.00010 | $0.00394 |
| Sonnet 5 | $0.00004 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
specrew-where 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specrew-where
Type: Operational Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-where
Purpose
Show the current Specrew project status dashboard — the "where am I?" velocity view for the active feature and iteration.
When to Use
- When a contributor wants to know the current project status, active feature, and iteration state.
- When checking progress against iteration capacity.
- When troubleshooting stale or unexpected lifecycle state.
- Invoke this skill when the user asks: "Where am I?", "Show me the Specrew dashboard", "What is the current status?", or "What feature is active?"
Boundary Safety
This skill provides read-only status information only. Invoking /specrew-where does not authorize or imply approval to advance any lifecycle boundary. Human review is still required for lifecycle transitions.
Invocation
/specrew-where [--project-path <path>] [--feature <id>] [--iteration <NNN>]
[--compact] [--ascii] [--no-color] [--json]
[--team] [--worktrees] [--recentcount <N>] [--barwidth <N>]
Backed by: specrew where / scripts/specrew-where.ps1
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
--project-path |
string | No | Target Specrew project path (defaults to current directory) |
--feature |
string | No | Restrict view to a specific feature directory under specs\ |
--iteration |
string | No | Restrict view to a specific iteration number |
--compact |
flag | No | Emit a compact single-line summary |
--ascii |
flag | No | Use ASCII-safe output (no Unicode box-drawing) |
--no-color |
flag | No | Suppress color output |
--json |
flag | No | Emit machine-parseable JSON output |
--team |
flag | No | Include team member status in the view |
--worktrees |
flag | No | Include worktree awareness information |
--recentcount |
number | No | Number of recent iterations to include (default: 6) |
--barwidth |
number | No | Width of progress bar in characters (default: 28) |
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 · 81 lines · 20 tokens per session scan A ccfef2f36d8e
specrew-where is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 788 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…