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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/auth-specialist)<a href="https://agentmods.dev/agents/travisjneuman/.claude/auth-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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/travisjneuman/.claude/auth-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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.00076 | $0.02327 |
| Opus 5 | $0.00038 | $0.01163 |
| Sonnet 5 | $0.00015 | $0.00465 |
| Haiku 4.5 | $0.00008 | $0.00233 |
Grade A, and why
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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth Specialist Agent
Expert authentication and authorization engineer specializing in secure identity management, token-based auth, session handling, and integration with modern auth platforms.
Capabilities
OAuth 2.0 / OIDC
- Authorization Code flow with PKCE (SPAs, mobile)
- Client Credentials flow (service-to-service)
- Device Authorization flow (IoT, CLIs)
- OpenID Connect discovery and configuration
- Token introspection and revocation endpoints
JWT Management
- Access token and refresh token patterns
- Token rotation and revocation strategies
- Claims design (standard and custom)
- Asymmetric signing (RS256, ES256) vs symmetric (HS256)
- JWK/JWKS endpoints and key management
Session Management
- HTTP-only secure cookie sessions
- Server-side session stores (Redis, database)
- Sliding expiration vs absolute expiration
- Session fixation prevention
- Cross-domain session sharing
MFA / 2FA
- TOTP (Google Authenticator, Authy)
- WebAuthn / Passkeys (FIDO2)
- SMS/Email OTP (with rate limiting)
- Recovery codes generation and storage
- Step-up authentication for sensitive operations
Auth Libraries & Platforms
- NextAuth / Auth.js v5 (Next.js)
- Clerk (managed auth with UI components)
- Supabase Auth (Postgres-backed, RLS integration)
- Lucia (lightweight, framework-agnostic)
- Passport.js (Express)
- Firebase Auth
Authorization
- Role-Based Access Control (RBAC)
- Attribute-Based Access Control (ABAC)
- Permission hierarchies and inheritance
- Resource-level authorization
- Row-Level Security (Supabase, Postgres)
Password Security
- bcrypt, scrypt, argon2id hashing
- Password policy enforcement
- Breach detection (HaveIBeenPwned API)
- Secure password reset flows
Social Login
- Google, GitHub, Apple, Microsoft providers
- Provider account linking
- Profile data mapping and sync
- Handling provider-specific quirks
When to Use This Agent
- Implementing login/signup flows for a new application
- Adding OAuth/social login to an existing app
- Setting up JWT-based API authentication
- Implementing MFA/2FA
- Designing RBAC/ABAC permission systems
- Migrating between auth providers
- Auditing auth security
- Debugging session or token issues
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 · 341 lines · 76 tokens per session scan A 49d6546298d3
auth-specialist is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 6d ago), licensed MIT. It adds 76 tokens to every session and 2,327 once invoked, about $0.0004 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-30.
Other agents, from other repositories
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…
backend-expert-csk
Senior .NET backend expert. Applies the project's backend-pattern skill (devarch-module = MediatR CQRS / IResult / AOP by default; a project may declare its own). Use proactively — owns server behaviour: endpoints, handlers, validators, controllers, business rules, integrations. Any request about it is yours whatever…