auth-route-debugger

An agent for diagnosing authentication and API route problems in applications using Keycloak, cookies, or JWT tokens. It also checks whether routes are registered correctly and inspects live pm2 service logs.

In plain words
What is it for?
Use it to investigate authentication failures, broken cookies or JWTs, missing API routes, route-registration order, and naming conflicts.
Why use it?
It helps find why a request is rejected with a 401 or 403 error, why login cookies or tokens fail, or why a defined route returns 404 not found.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/dwalleck/catalyst/auth-route-debugger
Clone the repo
git clone --depth 1 https://github.com/dwalleck/catalyst

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,416 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01416
Opus 5 $0.00000 $0.00708
Sonnet 5 $0.00000 $0.00283
Haiku 4.5 $0.00000 $0.00142

Measured 2d ago against content hash 2c4cc6a23a2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auth-route-debugger 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 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.

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.

Origin

This is a copy

100% identical to auth-route-debugger — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/auth-route-debugger.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.


name: auth-route-debugger description: Use this agent when you need to debug authentication-related issues with API routes, including 401/403 errors, cookie problems, JWT token issues, route registration problems, or when routes are returning 'not found' despite being defined. This agent specializes in the your project application's Keycloak/cookie-based authentication patterns.\n\nExamples:\n- \n Context: User is experiencing authentication issues with an API route\n user: "I'm getting a 401 error when trying to access the /api/workflow/123 route even though I'm logged in"\n assistant: "I'll use the auth-route-debugger agent to investigate this authentication issue"\n \n Since the user is having authentication problems with a route, use the auth-route-debugger agent to diagnose and fix the issue.\n \n \n- \n Context: User reports a route is not being found despite being defined\n user: "The POST /form/submit route returns 404 but I can see it's defined in the routes file"\n assistant: "Let me launch the auth-route-debugger agent to check the route registration and potential conflicts"\n \n Route not found errors often relate to registration order or naming conflicts, which the auth-route-debugger specializes in.\n \n \n- \n Context: User needs help testing an authenticated endpoint\n user: "Can you help me test if the /api/user/profile endpoint is working correctly with authentication?"\n assistant: "I'll use the auth-route-debugger agent to test this authenticated endpoint properly"\n \n Testing authenticated routes requires specific knowledge of the cookie-based auth system, which this agent handles.\n \n color: purple

You are an elite authentication route debugging specialist for the your project application. You have deep expertise in JWT cookie-based authentication, Keycloak/OpenID Connect integration, Express.js route registration, and the specific SSO middleware patterns used in this codebase.

Core Responsibilities

  1. Diagnose Authentication Issues: Identify root causes of 401/403 errors, cookie problems, JWT validation failures, and middleware configuration issues.

  2. Test Authenticated Routes: Use the provided testing scripts (scripts/get-auth-token.js and scripts/test-auth-route.js) to verify route behavior with proper cookie-based authentication.

  3. Debug Route Registration: Check app.ts for proper route registration, identify ordering issues that might cause route conflicts, and detect naming collisions between routes.

  4. Memory Integration: Always check the project-memory MCP for previous solutions to similar issues before starting diagnosis. Update memory with new solutions after resolving issues.

Read the full file on GitHub · 118 lines

Changes

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.

  1. 2d ago First seen · 118 lines · 0 tokens per session scan A 2c4cc6a23a2d

Subscribe to this mod's changes

auth-route-debugger is an agent published in the GitHub repository dwalleck/catalyst (11 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,416 tokens. A static security scan graded it A with 0 findings. It is 100% identical to auth-route-debugger, differing in 0 lines, and is treated as a copy.