Security — no service client in client code, no SUPABASE_SECRET_KEY on client, RLS, correct Supabase client per context, rate limit config, SSR state rules (no authenticationRepository in server load, ssr = false for protected routes)
1024d agoReviewMountCreate a free account to mount
Open Code Review - AI code quality gate for detecting hallucinated packages, stale APIs, context breaks, security anti-patterns, and over-engineering in AI-generated code.
378mo agoReviewMountCreate a free account to mount
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
224mo agoReviewMountCreate a free account to mount
Blunt, factual code review. No sugar coating. Finds bugs, security issues, performance problems, and architecture flaws. Use when user says /codereview or asks to review code.
GitHub Actions workflow review, scaffolding, and security hardening. Use when user says 'review my workflow', 'check my actions', 'scaffold a workflow', 'is my CI correct', 'pin actions', 'OIDC to AWS', or when working in .github/workflows/*.yml files.
seatbelt — pre-ship safety rules. Stops secrets in client code or git, tables without row security, routes without auth, open CORS, unverified webhooks.
Reviews designs and diffs for security and privacy risk - auth, access control, secrets, injection, dependencies, data exposure. It writes its report and never changes code. Use on any feature touching accounts, payments, personal data, file upload or a new integration.
Apply PsyLinks 360° Security Review when working on authentication, APIs, backend services, databases, secrets, dependencies, deployment, or AI-agent/MCP workflows.
Audit websites for SEO, performance, security, technical, content, and 15 other issue cateories with 230+ rules using the squirrelscan CLI. Returns LLM-optimized reports with health scores, broken links, meta tag analysis, and actionable recommendations. Use to discover and asses website or webapp issues and health.
224mo agoReviewMountCreate a free account to mount
Capability-security review of PRs, diffs, or third-party/plugin code — apply when reviewing pull requests, auditing contributed code, or judging whether code is safe.
Use when reviewing a diff, pull request, or code change — systematic checklist for correctness, clarity, security, testability, and adherence to the project's conventions. Covers what to look for, how to give actionable feedback, and when to approve vs. request changes.
Use when writing any query, migration, or test that touches tenant data in this repository. Covers withOrgScope and withWorkerScope, the two Postgres roles and why the boundary is in the database rather than in a lint rule, the shape a row-level security policy has to take, when Effect.orDie is right, and why a fixture seeds through the product's own write path.
ALWAYS invoke when the user mentions Saltzer (e.g., 'Saltzer', 'ask Saltzer', 'run Saltzer', 'consult Saltzer') or asks for security review, vulnerability assessment, pen-testing, or pre-release audit. Principal Application
Senior code reviewer. Use after code changes or on a PR/diff to find real bugs, security issues, and risky changes, ranked BLOCKER to NIT with file:line and a concrete failure scenario. Read-only.