Borrowing it
Nothing to install: this file belongs to SylphxAI/pdf-reader-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SylphxAI/pdf-reader-mcp/main/.opencode/command/saas-growth.mdgit clone --depth 1 https://github.com/SylphxAI/pdf-reader-mcpWrote 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/commands/sylphxai/pdf-reader-mcp/saas-growth)<a href="https://agentmods.dev/commands/sylphxai/pdf-reader-mcp/saas-growth"><img src="https://agentmods.dev/badge/commands/sylphxai/pdf-reader-mcp/saas-growth/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/commands/sylphxai/pdf-reader-mcp/saas-growth"><img src="https://agentmods.dev/badge/commands/sylphxai/pdf-reader-mcp/saas-growth.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.00017 | $0.00799 |
| Opus 5 | $0.00009 | $0.00400 |
| Sonnet 5 | $0.00003 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
saas-growth 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 3d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Systems Review
Scope
Review growth systems: onboarding flows, referral program, retention mechanics, viral/sharing features, and user guidance.
Specification
Growth System Foundation
- The system must produce a coherent, measurable growth system for activation, sharing/virality, and retention, aligned with compliance and anti-abuse constraints.
Onboarding
- Onboarding must be outcome-oriented (guide to first value, not just feature tour).
- Localized for all supported locales.
- Accessible (WCAG AA).
- Instrumented (track completion, drop-off points).
- Progressive disclosure — don't overwhelm new users.
Sharing/Virality
- Sharing must be consent-aware (no spam, no dark patterns).
- Abuse-resistant with rate limiting and detection.
- Measurable end-to-end (share → click → signup → conversion).
- Platform-appropriate sharing (native share sheet on mobile, copy link on desktop).
Retention
- Retention must be intentionally engineered, not accidental.
- Monitored with cohort analysis.
- Protected against regressions (alert on retention drops).
- Re-engagement flows (email, push) must be consent-governed.
Referral Program (Anti-Abuse Baseline Required)
-
Referral must be measurable, abuse-resistant, and governed:
- Clear attribution semantics (who referred whom, when)
- Reward lifecycle governance (pending → approved → paid, including revocation/clawbacks)
- Anti-fraud measures
- Admin reporting and audit capabilities
- Localized and instrumented
-
Referral anti-fraud minimum baseline is mandatory:
- Define minimum set of risk signals and enforcement measures
- Velocity controls (rate limiting referrals)
- Account/device linkage posture (detect self-referral)
- Risk-tiered enforcement (high-risk delays, low-risk instant)
- Reward delay/hold/freeze capabilities
- Clawback conditions clearly defined
- Auditable manual review/appeal posture where applicable
Support and Communications
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.
- 3d ago First seen · 95 lines · 17 tokens per session scan A 5381583a62b2
saas-growth is a command published in the GitHub repository SylphxAI/pdf-reader-mcp (921 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 799 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-06.
Other commands, from other repositories
latex-polish
Inspect a cleanly compiling LaTeX document for source pathologies and rendered visual defects by linting and viewing selected PDF pages. Use when compilation succeeds but title pages, floats, tables, figures, or layout still need publication-quality review. Not for basic compilation health; use $latex-health-check.
latex
Compile one specified LaTeX document, resolve build errors, audit citations, and report build quality. Use when a .tex source must be built or a concrete compilation failure repaired. Not for corpus-wide build checks, visual polish after a clean build, or creating a project; use $latex-health-check, $latex-polish, or…
bib-filter
Filter a LaTeX project's bibliography to the entries actually cited, with Overleaf-source resolution, temporary staging, validation, approval-gated canonical replacement, and compilation. Use before submission or after large revisions.
bib-parse
Extract citations from a PDF and generate a validated .bib file. Use when the user asks to extract citations from a PDF and generate a validated .bib file. Reads the PDF, identifies referenced works, constructs BibTeX entries, and verifies metadata.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
insights-deck
Archive an exported Claude Code insights HTML report and turn it into a timestamped Beamer presentation usable from either client. Use when the insights export is the source artifact for a presentation. Not for a general research talk; use $talk-deck.