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-admin.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-admin)<a href="https://agentmods.dev/commands/sylphxai/pdf-reader-mcp/saas-admin"><img src="https://agentmods.dev/badge/commands/sylphxai/pdf-reader-mcp/saas-admin.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.00990 |
| Opus 5 | $0.00011 | $0.00495 |
| Sonnet 5 | $0.00004 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
saas-admin 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 yesterday.
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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Admin Platform Review
Scope
Review admin systems: RBAC, bootstrap flow, configuration management, feature flags governance, operational tooling, and impersonation.
Specification
Access Control (RBAC)
- Least privilege principle: Users get minimum permissions needed.
- Role hierarchy with clear inheritance.
- Permission granularity (resource-level, action-level).
- All authorization is server-enforced; no client-trust.
- Role changes require appropriate privilege level and are audited.
Admin Bootstrap (Hard Requirement)
- Admin bootstrap must not rely on file seeding.
- Use a secure, auditable first-login allowlist for the initial SUPER_ADMIN.
- Permanently disable bootstrap after completion — no re-entry.
- All privilege grants must be server-enforced and recorded in the audit log.
- The allowlist must be managed via secure configuration (environment/secret store), not code or DB seeding.
Configuration Management
- All non-secret product-level configuration must be manageable via admin (server-enforced).
- Configuration changes require validation and change history.
- Secrets/credentials are environment-managed only; admin may expose safe readiness/health visibility, not raw secrets.
- Support for environment-specific overrides (dev/staging/prod).
- Rollback capability for configuration changes.
Feature Flags Governance
- Gradual rollout support (percentage-based, user segment-based).
- A/B testing integration where applicable.
- Audit trail for all flag changes (who/when/why).
- Emergency kill switches for rapid disable.
- Flag lifecycle management (created → active → deprecated → removed).
- Server-enforced evaluation; no client-side flag source-of-truth.
Operational Management
-
User/account management tools:
- Search, view, edit user profiles
- Account status management (active, suspended, banned)
- Manual verification/unverification
-
Entitlements/access management:
- View and modify user entitlements
- Grant/revoke access with audit trail
- Bulk operations with safeguards
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.
- yesterday First seen · 124 lines · 22 tokens per session scan A 371541d8ffe7
saas-admin is a command published in the GitHub repository SylphxAI/pdf-reader-mcp (917 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 990 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
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.
latex-health-check
Compile all LaTeX projects and report cross-project build consistency. Use when checking whether a collection of papers builds cleanly. Not for rendered visual inspection after a clean build; use $latex-polish.
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.