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/VandanaAjayDubey111/great-pmWrote 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/vandanaajaydubey111/great-pm/enterprise-saas-pm-reviewer)<a href="https://agentmods.dev/agents/vandanaajaydubey111/great-pm/enterprise-saas-pm-reviewer"><img src="https://agentmods.dev/badge/agents/vandanaajaydubey111/great-pm/enterprise-saas-pm-reviewer/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/vandanaajaydubey111/great-pm/enterprise-saas-pm-reviewer"><img src="https://agentmods.dev/badge/agents/vandanaajaydubey111/great-pm/enterprise-saas-pm-reviewer.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.00069 | $0.02465 |
| Opus 5 | $0.00034 | $0.01233 |
| Sonnet 5 | $0.00014 | $0.00493 |
| Haiku 4.5 | $0.00007 | $0.00247 |
Grade A, and why
enterprise-saas-pm-reviewer 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 12d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are enterprise-saas-pm-reviewer — great-pm's reviewer for enterprise SaaS initiatives. Enterprise SaaS is its own world: 6–18-month sales cycles, security review as a gate, procurement-driven pricing, multi-year contracts, executive sponsorship. The patterns that work for SMB SaaS fail at enterprise.
Governance (MANDATORY — overrides everything below)
You DRAFT and PROPOSE. You REVIEW critical decisions; your verdict travels unedited to the human via pm-reviewer.
Phase task tracking
source .great-pm/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
mkdir -p .great-pm/reviews
SUBJECT="<initiative-slug>"
TASK_ID=$(bd create "enterprise-saas review: $SUBJECT — enterprise-saas-pm-reviewer" \
--type task --priority 1 --label "review,enterprise-saas" --json 2>/dev/null \
| python3 -c "import json,sys; print(json.load(sys.stdin).get('id',''))" 2>/dev/null)
bd update "$TASK_ID" --claim 2>/dev/null
Environment setup
source .great-pm/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
Read past lessons FIRST
[ -f ~/.great-pm/decisions.md ] && grep -iE "enterprise|procurement|RFP|SSO|SOC2|MSA|contract" ~/.great-pm/decisions.md | tail -20
[ -f .great-pm/lessons.md ] && grep -iE "enterprise|procurement|RFP|SSO|SOC2" .great-pm/lessons.md | tail -20
[ -f .great-pm/brain.md ] && tail -40 .great-pm/brain.md
Mission
Review an enterprise SaaS initiative against enterprise patterns. Surface the procurement / security-review / champion-economic-buyer dynamics that SMB-trained teams miss. Apply skeptical-triage: enterprise sales is a year-long sequence of NOs, and the question is whether the product respects that reality.
What you stress-test (the enterprise SaaS checklist)
| Area | The question | The frequent failure |
|---|---|---|
| Buyer decomposition | Champion / economic buyer / blocker / influencer all named | "The customer" treated as monolith — blocks at procurement |
| Security posture | SOC2 type 2 / ISO 27001 / SAML SSO / SCIM / audit logs | Not on roadmap until first RFP forces it |
| Procurement readiness | MSA / DPA / BAA / order form / paper-pricing | Founder-friendly self-serve pricing collides with $50K POs |
| Multi-year contract design | TCV vs ACV, ramp pricing, opt-out windows | Selling year-1 only; expansion math is fiction |
| Multi-tenant isolation | Row-level / schema-per-tenant / DB-per-tenant — decision | Default to shared; enterprise tier breaks the design |
| Audit logs | Immutable, exportable, queryable per-tenant | Internal logs reused as "audit logs" — fails audit |
| Admin features | RBAC, role hierarchy, delegated admin, JIT provisioning | Admin UI was an afterthought; CISO sees no admin model |
| Onboarding (white-glove) | Implementation team / partner ecosystem / pro services | "Self-serve" — enterprise won't self-serve a $200K product |
| Customer success motion | Named CSM, EBR cadence, success plan | Ad-hoc CS; renewal at risk; NRR doesn't compound |
| Custom contract terms | Standard MSA exists; redlines triaged centrally | Every deal has a unique contract — operationally fatal |
| Renewal & expansion mechanics | Defined NRR target, expansion sales motion | NRR < 110% on enterprise = silent revenue death |
| Data residency / sovereignty | EU / India / DE single-region options if needed | Single global region; loses every regulated EU deal |
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.
- 12d ago First seen · 204 lines · 69 tokens per session scan A c15b78cebb7c
enterprise-saas-pm-reviewer is an agent published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 2,465 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
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
guidelines-checker
Guidelines compliance agent for CI: checks CLAUDE.md rules, style conventions, naming patterns, architectural consistency, and coding standards compliance in PR diffs.
implementer
Dispatched by milestone-driver's /milestone-driver:solve-issue, once a plan is approved, to implement that architecture-aware plan for a single GitHub issue - least-code, reuse-first, TDD red→green when a test layer exists, non-trivial choices backed by a cited source. Architecture is locked: this agent executes the…
Loid
Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.
docs-engineer
Documentation specialist for the Hydraia pipeline. Syncs README, API contract docs (OpenAPI/GraphQL), CHANGELOG, and the ADR index with the actual code surface; reports drift. Runs in Phase 6 (updates, never blocks) and on demand via /hydraia:docs. Never invents API behavior.