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.
npx skills add ShipWithAI/shipwithai-plugins --skill auth-doctorgit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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/skills/shipwithai/shipwithai-plugins/auth-doctor)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/auth-doctor"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/auth-doctor/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/skills/shipwithai/shipwithai-plugins/auth-doctor"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/auth-doctor.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.00042 | $0.03854 |
| Opus 5 | $0.00021 | $0.01927 |
| Sonnet 5 | $0.00008 | $0.00771 |
| Haiku 4.5 | $0.00004 | $0.00385 |
Grade A, and why
auth-doctor 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 9d 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth Doctor — Diagnostic Guide
Health check for existing authentication setups. Detects misconfigurations, missing files, security issues, and dangerous code patterns across Better Auth and Firebase Auth projects.
When to Use
- After running
/shipwithai-auth:setup— final validation - Auth is broken and you don't know why
- Before deploying to production — pre-flight check
- After upgrading auth packages or Next.js version
- Periodic maintenance check
Step 1: Auto-Discover Project Stack
Run the same discovery logic as skills/auth-setup/SKILL.md → Step 0. This ensures setup and doctor use identical detection.
Scan for:
1a. Framework & Versions (same as setup Step 0a/0b):
next.config.*→ Next.js (extract version frompackage.json)- App Router vs Pages Router
- React version, Node.js version
1b. Auth Provider (same as setup Step 0d):
better-authin deps → Better Authfirebasein deps → Firebase@clerk/nextjs,next-auth,@supabase/ssr→ respective provider- If no auth detected → ❌ STOP: "No auth setup detected. Run
/shipwithai-auth:setupfirst."
1c. ORM & Database (same as setup Step 0c):
drizzle.config.ts→ Drizzle |prisma/schema.prisma→ Prisma- Check database type from drizzle config or deps (SQLite, PostgreSQL, MySQL)
1d. Package Manager (same as setup Step 0f):
- Lockfile detection
1e. UI Library (same as setup Step 0g):
components.json→ shadcn/ui | Tailwind | MUI/Chakra/Mantine
1e. Existing Auth Pages & Routes (same as setup Step 0e):
- Check for auth pages:
src/app/(auth)/login/,src/app/(auth)/register/, etc. - Check for API routes:
src/app/api/auth/ - Check for middleware:
src/middleware.ts,middleware.ts
1f. Auth-specific detection:
.env.localor.env→ configured env vars- OAuth providers: check env vars for
GOOGLE_CLIENT_ID,GITHUB_CLIENT_ID,APPLE_CLIENT_ID - Email: check for
resendin deps orRESEND_API_KEYin env
Output the detection summary before proceeding:
🔍 Auth Doctor — Scanning project...
Framework: Next.js 14.2.18 (App Router)
Provider: Better Auth ([email protected])
ORM: Drizzle ([email protected])
Database: SQLite (better-sqlite3)
Package mgr: npm
UI: shadcn/ui (new-york)
OAuth: Google ✓, GitHub ✗
Email: Resend ✓
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.
- 9d ago First seen · 385 lines · 42 tokens per session scan A 3243aa0dc39b
auth-doctor is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 26d ago), licensed MIT. It adds 42 tokens to every session and 3,854 once invoked, about $0.0002 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 skills, from other repositories
sdd-apply
Skill "sdd-apply" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, purpose, what you receive and execution and persistence contract.
memstack-automation-webhook-designer
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification', 'idempotency', or needs secure webhook handlers with signature verification, retry handling, and dead letter queues. Do NOT use for full n8n workflows or scheduled tasks.
shopify-apps
Shopify app development - Remix, Admin API, checkout extensions.
aws-aurora
AWS Aurora Serverless v2, RDS Proxy, Data API, connection pooling.
supabase-node
Express/Hono with Supabase and Drizzle ORM.
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…