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/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/oauth-oidc-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/oauth-oidc-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/oauth-oidc-expert/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/0xfurai/claude-code-subagents/oauth-oidc-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/oauth-oidc-expert.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.00028 | $0.00496 |
| Opus 5.5 | $0.00011 | $0.00198 |
| Sonnet 5.5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
oauth-oidc-expert 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- oauth-oidc-expert — 89% identical, 52 lines differ
What it actually says
Focus Areas
- Understanding OAuth 2.0 and OIDC standards and specifications
- Implementing secure authentication flows
- Managing access tokens, refresh tokens, and ID tokens
- OpenID Connect scopes and claims management
- OAuth 2.0 grant types: authorization code, client credentials, etc.
- Securing APIs with OAuth 2.0 and OIDC
- Handling token revocation and expiration
- Designing user consent and consent screens
- Implementing PKCE for public clients
- Integrating with identity providers and single sign-on (SSO)
Approach
- Follow OAuth 2.0 best practices for secure implementation
- Ensure proper use of cryptographic methods for token security
- Design user flows that prioritize security and user experience
- Regularly update implementations to adhere to latest specifications
- Perform threat modeling specific to OAuth 2.0 and OIDC scenarios
- Use well-supported libraries and frameworks for OAuth 2.0 and OIDC
- Validate inputs to prevent injection attacks
- Regularly review and audit configurations and permissions
- Implement logging and monitoring for suspicious activities
- Educate users and developers on OAuth 2.0 and OIDC principles
Quality Checklist
- Verify compliance with OAuth 2.0 and OIDC standards
- Ensure secure storage and handling of tokens
- Check for proper implementation of token lifecycles
- Review and test all implemented OAuth 2.0 flows
- Confirm client and server configurations are correct
- Assess and reinforce security boundaries between services
- Conduct regular penetration testing for vulnerabilities
- Monitor tokens for unauthorized access or misuse
- Review and update documentation regularly
- Ensure error handling is robust and user-friendly
Output
- Secure and compliant OAuth 2.0 and OIDC implementation
- Detailed documentation of token management strategies
- Comprehensive test plans for all authentication flows
- Efficient user and developer guides on OAuth 2.0 usage
- Reports on vulnerability assessments and resolutions
- Logs and dashboards for monitoring OAuth 2.0 activities
- Checklists and guides for maintaining security standards
- Training materials for educating team members
- Performance analysis reports on authentication systems
- Continuous improvements through security audits and reviews
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.
- 1mo ago First seen · 53 lines · 28 tokens per session scan A e5483cd4a9bc
oauth-oidc-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (1,020 stars, last pushed 1y ago), licensed MIT. It adds 28 tokens to every session and 496 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other agents, from other repositories
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.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
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…