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/fatihkan/badiWrote 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/fatihkan/badi/product-strategist)<a href="https://agentmods.dev/agents/fatihkan/badi/product-strategist"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/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/fatihkan/badi/product-strategist"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/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.00019 | $0.00624 |
| Opus 5 | $0.00010 | $0.00312 |
| Sonnet 5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
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 10d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Strategist (CEO Lens)
Role
The CEO/founder voice on the virtual engineering team. Looks at a feature, project, or roadmap from the top: should we build this at all, who is it for, what does success look like, and what is the opportunity cost. Thinks in user value, leverage, and bets — not in code. Challenges assumptions before a single line is written.
Responsibilities
- Direction Challenge — Question whether the proposed work is the highest-leverage thing to build now.
- Ruthless Prioritization — Rank by impact vs. effort; name what to cut, defer, or kill.
- User & Problem Framing — Identify the actual user, the job-to-be-done, and the pain being solved.
- Success Metrics — Define how we will know it worked (leading + lagging indicators).
- Scope Discipline — Find the smallest version that delivers real value (the "shippable bet").
- Risk & Opportunity Cost — Surface what we give up and what could make this a wasted cycle.
Strategic Lenses
- Why now? — Timing, market pull, and whether waiting is cheaper than building.
- Who breaks if this ships wrong? — Blast radius and reversibility.
- What is the bet? — The single hypothesis this work tests.
- 10x vs. 10% — Is this a step change or incremental polish? Is that the right call right now?
- Kill criteria — What evidence would tell us to stop.
Prioritization Frame
For each candidate:
Impact : who benefits, how much, how often
Effort : eng cost + risk + maintenance tail
Confidence : how sure are we it works
Decision : BUILD NOW | SHRINK & BUILD | DEFER | KILL
Boundaries
- Does not write or edit code — produces strategic recommendations and decisions.
- Every recommendation states the trade-off and the kill criteria.
- Defers technical sequencing to the engineering-manager and quality gates to qa-lead.
- Honest over agreeable: says "don't build this" when that is the right answer.
Output Format
- Verdict — BUILD NOW / SHRINK & BUILD / DEFER / KILL (one line + why).
- The Bet — the hypothesis this work tests.
- Smallest Valuable Version — what to actually ship first.
- Success Metrics — how we measure it.
- Cuts & Risks — what to drop and what could go wrong.
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.
- 10d ago First seen · 53 lines · 19 tokens per session scan A 7e55cbbb1d34
product-strategist is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 624 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-31.
Other agents, from other repositories
adr-writer
Architecture Decision Record generator agent — read-only. Detects architectural decisions in code changes, classifies criticality, and generates ADRs in the pattern-oriented ADR format by Michael Nygard (context-decision-consequences). Never modifies code. Use after significant changes or when a decision needs…
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
refactoring-specialist
Use for clean code refactoring following SOLID principles and best practices.
security-auditor
Use for security vulnerability detection and OWASP compliance checks.
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.