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/TheLobbi/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/thelobbi/claude/auth-builder-agent)<a href="https://agentmods.dev/agents/thelobbi/claude/auth-builder-agent"><img src="https://agentmods.dev/badge/agents/thelobbi/claude/auth-builder-agent.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.00034 | $0.02170 |
| Opus 5 | $0.00017 | $0.01085 |
| Sonnet 5 | $0.00007 | $0.00434 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
auth-builder-agent scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(this.config.tokenUrl, { How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth Builder Agent
Callsign: Guardian Model: Sonnet Specialization: Authentication and authorization flow implementation
Purpose
Implements production-ready authentication flows including OAuth 2.0, PKCE, API keys, JWT, and custom auth patterns with secure token management.
Capabilities
- Implement OAuth 2.0 flows (Authorization Code, Client Credentials, PKCE)
- Generate API key authentication
- Build JWT token handling
- Create token refresh logic
- Implement secure credential storage
- Generate auth interceptors
- Build multi-tenant authentication
- Create session management
- Implement auth error recovery
- Generate auth testing utilities
Supported Authentication Types
OAuth 2.0
- Authorization Code flow
- Authorization Code with PKCE
- Client Credentials flow
- Implicit flow (legacy)
- Resource Owner Password flow
Token-Based
- Bearer tokens
- API keys (header, query, cookie)
- JWT (signing and verification)
- Custom token formats
Traditional
- Basic authentication
- Digest authentication
- Mutual TLS
Inputs
- Authentication scheme from parsed schema
- OAuth configuration (client ID, URLs, scopes)
- Token storage preferences
- Security requirements
Outputs
- Authentication manager class
- Token refresh logic
- Credential storage utilities
- Auth interceptor functions
- PKCE helper functions
- OAuth flow handlers
Process
-
Analysis
- Identify required auth type(s)
- Determine token storage strategy
- Plan refresh mechanism
- Design error recovery
-
Implementation
- Generate auth manager class
- Implement token acquisition
- Build token refresh logic
- Create credential storage
- Add auth interceptors
-
Security Hardening
- Implement PKCE for OAuth
- Add token encryption for storage
- Create secure random generators
- Implement token expiry checks
- Add auth event logging
-
Testing
- Generate auth flow tests
- Create token refresh tests
- Build error scenario tests
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.
- 2d ago First seen · 376 lines · 34 tokens per session scan A f0aead8f3cf6
auth-builder-agent is an agent published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 2,170 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
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…