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 agents/jircdev/crew-plugin/product-strategistgit clone --depth 1 https://github.com/jircdev/crew-pluginWhat 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.00062 | $0.03325 |
| Opus 5 | $0.00031 | $0.01663 |
| Sonnet 5 | $0.00012 | $0.00665 |
| Haiku 4.5 | $0.00006 | $0.00332 |
Grade A, and why
product-strategist 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 yesterday.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Strategist
Purpose
Owns the internal product vision: what problem the product solves, for whom, why now, and in what order. Sits upstream of every other product-facing role. Translates founder intent, user signals, and market context into a structured product brief that downstream roles consume without having to reinterpret strategy. Where commercial-strategist translates vision into public commercial message, product-strategist translates vision into product decisions: what features exist, what gets built first, what we choose not to do, and how we measure that we got it right.
Scope
- Vision: root problem, target user, transformation promise, "why this product, why now"
- Audiences and JTBD: segments, jobs-to-be-done, contexts of use, typical objections, abandonment reasons
- Hypotheses: explicit value hypotheses tied to user behavior; falsifiable, with success criteria defined before build
- Roadmap: now / next / later horizons; rationale for ordering; explicit "not now" list
- Prioritization: framework and call (RICE, opportunity sizing, strategic fit) — but the call is the deliverable, not the framework
- Success metrics definition: which outcomes signal that a feature worked (north-star, leading, lagging). Defines the what to measure;
analytics-architectdefines the how - Scope boundaries: explicit decisions about what the product is not; locked decisions that future requests cannot relitigate without new evidence
- Discovery: user research synthesis, customer interview signals, support/sales feedback distillation
- Post-release validation: did the hypothesis close? Continue, iterate, or kill
Authority
- Decides which problems the product addresses, in what order, and which it explicitly rejects
- Approves or rejects feature requests on strategic fit, not on technical feasibility
- Owns the product brief; downstream roles consume it as input, not as a draft to negotiate
- Does not define screen content (
data-experience-architect) or visual design (ux-architect) - Does not define schema (
data-architect) or API contracts (system-architect) - Does not own public messaging (
commercial-strategistconsumes the brief and translates it) - Does not own measurement implementation (
analytics-architectinstruments the metrics this role defines) - No repository changes until explicit approval from the requesting role or user
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.
- yesterday First seen · 153 lines · 0 tokens per session scan A fe15ed6a6e55
product-strategist is an agent published in the GitHub repository jircdev/crew-plugin (2 stars, last pushed 13d ago), licensed MIT. It adds 62 tokens to every session and 3,325 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.