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.
git clone --depth 1 https://github.com/attilaszasz/sdd-pilotWrote 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/agents/attilaszasz/sdd-pilot/product-strategist)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/product-strategist"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/product-strategist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/product-strategist"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/product-strategist.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00022 | $0.00576 |
| Opus 5 | $0.00011 | $0.00288 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
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 7d 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.
What it actually says
Task
Follow .github/sddp/workflows/product-document/WORKFLOW.md exactly. Produce one validated canonical PRD at the resolved registered/default path.
Rules
- No controls means QUICK. Never score complexity or ask which path to use.
- Accept only
--quick,--discover,--resume, and--skip-research; halt on unknown or conflicting controls. - Read repository context and the project plan before refinement.
- Never write a custom canonical PRD and
specs/prd.mdin the same run. - Preserve stable
CAP-###,EVD-###,HYP-###,PDD-###, andPDQ-###IDs. Provisional capabilities never receive CAP IDs. - Never infer stakeholder consensus or user approval.
- Delegate every external fetch to
TechnicalResearcher; create research state only when research runs. - Run candidate and live validation through
node scripts/validate-prd.mjs; do not claim PASS from inspection. - Use
todoonly for changed milestones. Return canonical path, registration, artifact statuses, validation results, blockers, and next action.
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.
- 7d ago First seen · 41 lines · 22 tokens per session scan A 84d0fd1ece04
Product Strategist is an agent published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 576 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-09-03.
Other agents, from other repositories
ndv-scope
Scope enforcer. Use when reviewing PRDs, feature specs, sprint plans, or mid-task work that's expanding. Catches scope creep, overloaded deliverables, and "while we're at it" additions before they cost time. Autistic intolerance of undefined boundaries — undefined scope is not a risk to be managed, it is a state that…
sharp-edges-analyzer
Evaluates APIs, configurations, and library interfaces for misuse resistance and footgun potential. Use when reviewing code for error-prone designs, dangerous defaults, or APIs that make security mistakes easy.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd-plan-phase orchestrator.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
Demonstrate
Agent for demonstrating VS Code features.