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 agentmods add agents/0xfurai/claude-code-subagents/keycloak-expertgit 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/keycloak-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/keycloak-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/keycloak-expert.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 | $0.00021 | $0.00435 |
| Opus 5 | $0.00010 | $0.00217 |
| Sonnet 5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
keycloak-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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Understanding Keycloak architecture and components
- Configuring realms, clients, and roles
- Setting up identity providers (IdP) and service providers (SP)
- Implementing authentication flows and required actions
- Managing users and groups
- User federation with LDAP and Active Directory
- Configuring password policies and credential storage
- Enabling auditing and logging for security compliance
- Securing applications with OIDC and SAML
- Automating Keycloak deployment and management with Ansible
Approach
- Begin with understanding requirements and existing IAM infrastructure
- Configure realms and clients to separate concerns
- Use roles and groups to manage access control effectively
- Set up identity providers to allow social login or SSO
- Use multi-factor authentication (MFA) for enhanced security
- Leverage user federation to integrate with external user databases
- Implement custom login themes for a seamless user experience
- Regularly update Keycloak instances to maintain security
- Use Keycloak REST API for automation and integration
- Monitor performance and optimize for scalability
Quality Checklist
- Realms and roles are configured as per organizational policy
- Authentication flows are tested with edge cases
- Multi-factor authentication is enabled where necessary
- User federation is correctly synchronized and monitored
- Password policies comply with security requirements
- Auditing and logging capture all necessary events
- Applications are tested for secure OIDC/SAML integration
- Custom themes enhance user experience without errors
- Automated scripts are reliable and recover from failures
- Regular backups and recovery plans are in place
Output
- Documented realm and client configurations
- Detailed setup instructions for identity providers
- Flow diagrams of authentication processes
- User migration and federation strategy
- Custom themes with clear branding guidelines
- Automated setup scripts with error handling
- Performance benchmarks and optimization reports
- Comprehensive test cases for login flows
- Audit logs and compliance reports
- Disaster recovery plans and documentation
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.
- 5d ago First seen · 58 lines · 21 tokens per session scan A 785182eaacfd
keycloak-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 21 tokens to every session and 435 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.