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-platform.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-platform)<a href="https://agentmods.dev/commands/sylphxai/pdf-reader-mcp/saas-platform"><img src="https://agentmods.dev/badge/commands/sylphxai/pdf-reader-mcp/saas-platform.svg" alt="Measured on agentmods" 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.00021 | $0.00709 |
| Opus 5 | $0.00010 | $0.00354 |
| Sonnet 5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
saas-platform 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 today.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend & Platform Review
Scope
Review frontend systems: design system, SEO implementation, PWA capabilities, performance optimization, and accessibility compliance.
Specification
Design System & UX
- Design-system driven UI (tokens for colors, spacing, typography).
- Dark/light theme support with user preference persistence.
- WCAG AA accessibility compliance.
- CLS-safe (no layout shift).
- Mobile-first responsive design; desktop-second.
- Iconify for icons; no emoji in UI content.
SEO Requirements
- SEO-first + SSR-first for indexable/discovery pages.
- Required metadata:
- Title and description (unique per page)
- Open Graph tags (og:title, og:description, og:image)
- Favicon (multiple sizes)
- Canonical URL
- robots meta tag
schema.orgstructured data where applicable.sitemap.xml(auto-generated, up-to-date).robots.txtproperly configured.
PWA Capabilities
- Web app manifest with proper icons and theme colors.
- Service worker with explicit cache correctness.
- Push notifications using VAPID where applicable.
- Service Worker caching boundary is mandatory: service worker must not cache personalized/sensitive/authorized content.
- Authenticated and entitlement-sensitive routes must have explicit cache-control and SW rules.
- SW caching boundaries must be validated by tests to prevent stale or unauthorized state exposure.
Performance
- Performance must be measurable and regression-resistant:
- Define and enforce performance budgets for key journeys
- Define caching boundaries and correctness requirements across SSR/ISR/static and service worker behavior
- Monitor Core Web Vitals and server latency; alert on regressions
- Target metrics:
- LCP < 2.5s
- FID < 100ms
- CLS < 0.1
- TTFB < 600ms
Guidance System
- Guidance is mandatory for all user-facing features and monetization flows.
- Must be: discoverable, clear, dismissible with re-entry option.
- Localized and measurable (track engagement).
- Governed by eligibility and frequency controls.
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.
- today First seen · 88 lines · 21 tokens per session scan A d6296f2ac583
saas-platform is a command published in the GitHub repository SylphxAI/pdf-reader-mcp (917 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 709 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
color-palette
Run the full colour workflow — tonal scales, semantic mapping, contrast checks, dark mode, and chart colours — and output a documented palette.
design-screen
Design a complete screen layout from a description or requirements.
responsive-audit
Audit a design's responsive behaviour across breakpoints — layout, touch targets, and content reflow.
type-system
Build a typography system end to end — scale, weights, line heights, measure, and responsive behaviour.
design-tokens
Définition Design Tokens.
style-guide
Generate comprehensive design system documentation including colors, typography, spacing, components, and usage guidelines. Outputs production-ready Tailwind/CSS configuration.