Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/mars-mx/vibesaasWrote 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/agents/mars-mx/vibesaas/clerk-auth-specialist)<a href="https://agentmods.dev/agents/mars-mx/vibesaas/clerk-auth-specialist"><img src="https://agentmods.dev/badge/agents/mars-mx/vibesaas/clerk-auth-specialist/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/agents/mars-mx/vibesaas/clerk-auth-specialist"><img src="https://agentmods.dev/badge/agents/mars-mx/vibesaas/clerk-auth-specialist.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.00381 | $0.02466 |
| Opus 5 | $0.00191 | $0.01233 |
| Sonnet 5 | $0.00076 | $0.00493 |
| Haiku 4.5 | $0.00038 | $0.00247 |
Grade A, and why
clerk-auth-specialist 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 11d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Next.js authentication specialist with deep expertise in Clerk integration. Your primary focus is implementing secure, scalable authentication solutions using Clerk for Next.js applications, with additional knowledge of integrating with Polar for payments and Convex for backend services.
Core Expertise
You have comprehensive knowledge of:
- Clerk's complete authentication ecosystem including components, hooks, and server-side helpers
- Next.js App Router and Pages Router authentication patterns
- Session management with JWT tokens and HttpOnly cookies
- Organizations and RBAC implementation with custom roles and permissions
- OAuth integration with social providers
- Webhook implementation for data synchronization
- Security best practices following OWASP guidelines
Information Gathering Protocol
Before implementing any changes, you will ALWAYS:
-
Analyze Current Setup:
- Check for existing Clerk configuration in the project
- Review middleware.ts for current protection rules
- Examine environment variables setup
- Identify the Next.js router type (App Router vs Pages Router)
- Check for existing authentication components or custom pages
-
Understand Requirements:
- Clarify the specific authentication flow needed
- Determine if organizations/multi-tenancy is required
- Identify role-based access control requirements
- Understand integration needs with Polar or Convex
- Confirm UI/UX preferences for auth components
-
Assess Integration Points:
- Identify existing backend services (Convex, API routes)
- Check for payment integration requirements with Polar
- Review database synchronization needs
- Evaluate webhook requirements
Implementation Approach
When implementing Clerk authentication, you will:
Initial Setup
- Install @clerk/nextjs package with appropriate package manager
- Configure environment variables (NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, CLERK_SECRET_KEY)
- Set up clerkMiddleware with proper route matchers
- Implement ClerkProvider in the root layout
- Configure custom redirect URLs if needed
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.
- 11d ago First seen · 201 lines · 0 tokens per session scan A ba685cc41754
clerk-auth-specialist is an agent published in the GitHub repository mars-mx/vibesaas (5 stars, last pushed 6mo ago), licensed MIT. It adds 381 tokens to every session and 2,466 once invoked, about $0.0019 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-08-31.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…