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-security.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-security)<a href="https://agentmods.dev/commands/sylphxai/pdf-reader-mcp/saas-security"><img src="https://agentmods.dev/badge/commands/sylphxai/pdf-reader-mcp/saas-security.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.00022 | $0.01100 |
| Opus 5 | $0.00011 | $0.00550 |
| Sonnet 5 | $0.00004 | $0.00220 |
| Haiku 4.5 | $0.00002 | $0.00110 |
Grade A, and why
saas-security 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security, Privacy & Compliance Review
Scope
Review security posture, privacy compliance, consent governance, observability systems, and operational readiness.
Specification
Security Baseline
- OWASP Top 10:2025 taxonomy awareness and mitigation.
- OWASP ASVS (L2/L3) verification baseline.
- Baseline controls:
- CSP (Content Security Policy) properly configured
- HSTS with appropriate max-age
- Security headers (X-Frame-Options, X-Content-Type-Options, etc.)
- CSRF protection where applicable
- Upstash-backed rate limiting
- Supply-chain hygiene (dependency audits)
- Security controls must be verifiable: CSP/HSTS/security headers and CSRF must be covered by automated checks or security tests and included in release gates.
- Risk-based anti-bot for auth and high-cost endpoints; integrate rate limits + consent gating.
Consent Governance (Release-Blocking)
- Behavioral consistency is required: policy and disclosures must match actual behavior across UI, data handling, logging/observability, analytics, support operations, and marketing tags; mismatches are release-blocking.
- Analytics (PostHog) and marketing/newsletter communications (Resend) must be governed by consent and user preferences.
- Marketing tags (including GTM and Google Ads) must not load or fire without appropriate consent.
- Without consent, tracking and marketing sends must not occur, except for strictly necessary service communications.
- Event schemas and attributes must follow data minimization, with explicit PII classification and handling rules.
Marketing Attribution (Hard Requirement)
- GTM may be used only for marketing tags and attribution; it must not become the primary product analytics system (PostHog remains the product analytics source).
- Conversions representing monetary value or entitlement changes must be server-truth aligned, idempotent, and deduplicated; client-side tags may exist for attribution but must not become the authoritative source of billing/entitlement truth.
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 · 109 lines · 22 tokens per session scan A 7992a5bd5d1a
saas-security is a command published in the GitHub repository SylphxAI/pdf-reader-mcp (917 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,100 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
compliance
SOC 2 compliance for Terraform — gap analysis, control implementation, evidence collection, and remediation guidance mapped to SOC 2 Trust Services Criteria.
venue-guidelines-compliance
Audit a paper and submission package against current official venue requirements for its venue, track, article type, cycle, and stage. Use when checking templates, limits, anonymity, declarations, or required files before submission or inside $pre-submission-report. Not for venue recommendations.
noirdoc-redact
Redact a local file via noirdoc, placing the clean copy in .noirdoc/cache/.
legal-doc
Create a professional legal document for enterprise use.
create-ui-component
Create a UI component with design system compliance and Storybook stories.
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.