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-user-profilenpx skills add alonf/specrew --skill specrew-user-profilegit 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-user-profile)<a href="https://agentmods.dev/skills/alonf/specrew/specrew-user-profile"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-user-profile.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.00031 | $0.01433 |
| Opus 5 | $0.00015 | $0.00717 |
| Sonnet 5 | $0.00006 | $0.00287 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
specrew-user-profile 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 5d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specrew-user-profile
Type: Configuration Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-user-profile
Purpose
Manage your Crew Interaction Profile — four decision-area settings that tell Specrew how much to
ask, explain, recommend, and auto-decide for you. Higher settings (7–10) get concise, expert-level
questions and assume you make the call; lower or auto settings get more explanation, recommended
defaults, and transparent auto-decisions.
The four visible decision areas are Product Strategy, UX/UI Design, Software Architecture, and AI Delivery Planning. They are display labels for collaboration settings — not job titles you must hold, and not Specrew's internal persona lenses (the perspectives the intake engine applies to your request). Your profile tunes how Specrew talks to you; the persona lenses are Specrew's internal analysis machinery and are unaffected by what you choose here.
The profile resolves per current user from a local file (the loader/path rule) and is reused across all Specrew projects:
- Windows:
$env:USERPROFILE\.specrew\user-profile.yml - Unix (Linux/macOS):
~/.specrew/user-profile.yml
When to Use
- When you want to view your current Crew Interaction Profile
- When you want to change how much Specrew asks/explains/auto-decides in one or more decision areas
- When you want to reset your profile and start fresh
- When troubleshooting substantive intake depth or question flow
Subcommands
show
Display the current Crew Interaction Profile with readable descriptions.
Invocation:
/specrew-user-profile show
Example output:
Crew Interaction Profile (current user):
- Product Strategy: 7 (Senior — concise questions; you decide)
- UX/UI Design: auto (Specrew recommends defaults and explains)
- Software Architecture: 9 (Senior — concise questions; you decide)
- AI Delivery Planning: 2 (Learning — Specrew explains and auto-decides with transparency)
To update: use /specrew-user-profile edit or /specrew-user-profile reset
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.
- 5d ago First seen · 180 lines · 31 tokens per session scan A 85603bc1ce23
specrew-user-profile is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 1,433 once invoked, about $0.0002 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…