caddy-security is a security application and set of plugins for Caddy v2, a web server, that handles user authentication and controls access to HTTP requests. It supports methods including local, LDAP, OpenID Connect, OAuth 2.0, SAML, JWT, and PASETO, and is used to protect web services behind Caddy.
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 skills add greenpau/caddy-security --skill break-fix-troubleshootinggit clone --depth 1 https://github.com/greenpau/caddy-securityWrote 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/skills/greenpau/caddy-security/break-fix-troubleshooting)<a href="https://agentmods.dev/skills/greenpau/caddy-security/break-fix-troubleshooting"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/break-fix-troubleshooting/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/skills/greenpau/caddy-security/break-fix-troubleshooting"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/break-fix-troubleshooting.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.00045 | $0.02105 |
| Opus 5.5 | $0.00018 | $0.00842 |
| Sonnet 5.5 | $0.00009 | $0.00421 |
| Haiku 4.5 | $0.00005 | $0.00211 |
Grade A, and why
break-fix-troubleshooting 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 today.
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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Break-Fix Troubleshooting
Purpose
Use this skill to turn a failing caddy-security deployment into either a
concrete fix or a high-quality break-fix report. Treat the repository skills in
.codex/skills as the primary task documentation; https://docs.authcrunch.com
is legacy context, not the source of truth.
Follow the repository scope when reproducing or fixing a report. A failure traced to go-authcrunch or an external plugin does not permit sibling edits or sibling build/test commands. Keep reproductions and reports here, identify the required upstream fix as separate work, and continue any correction that can be completed in this module.
Workflow
- Identify the intended auth flow, protected routes, observed symptom, expected behavior, and whether the failure happens during Caddyfile adaptation, provisioning, login, callback handling, authorization, upstream proxying, or token/session validation.
- Inspect supplied evidence first and gather only missing details that can
distinguish the likely causes: relevant Caddyfile, logs, HTTP/browser status,
caddy version,caddy security version,caddy list-modules --versions | rg '(auth|security)', operating environment, recent changes, and last known working version. Use the actual installed binary name; older binaries may lacksecurity version. - Redact secrets while preserving directive names, route structure, identity provider names, policy names, cookie names, issuer URLs, redirect paths, roles, claim names, and module versions.
- Use configuration to analyze Caddyfiles and select the affected authentication, authorization, identity, or runtime domain. Test selection and fixture/CI mechanics follow the testing contract.
- Compare the configuration to the parser files and fixtures named by the loaded skills. Prefer the smallest valid corrected configuration over a broad rewrite.
- Validate with the narrowest available command. Use Caddy adaptation or
focused Go tests when local context supports it; otherwise describe the exact
command the reporter should run. Adaptation does not prove runtime behavior;
validateandrunmay open identity files or contact providers. Reproduce with disposable local data before provisioning a supplied deployment config. - Report the root cause, the minimal fix, validation performed, remaining uncertainty, and any repository-skill gap discovered during the work.
- For an issue-preparation request or a useful unresolved handoff, write the
report under
tmp/breakfix/. A direct explanation or completed small fix does not automatically require an issue artifact; honor the requested deliverable.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 184 lines · 45 tokens per session scan A a51bffe7d908
break-fix-troubleshooting is a skill published in the GitHub repository greenpau/caddy-security (2,263 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 2,105 once invoked, about $0.0002 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-10-25.
Other skills, from other repositories
auth-patterns
Use when implementing authentication (JWT, sessions, OAuth), authorization (RBAC, ABAC), password hashing, MFA, or security best practices for backend services.
auth0-docs
Auth0 — identity platform: auth flows, Universal Login, SSO, identity providers, MFA, RBAC, Actions, tokens.
JWT Security Testing
Comprehensive JWT token security testing including signature verification, expiration checks, algorithm confusion attacks, and claim validation.
security-review
Security Code Review: Reviews code for security vulnerabilities including authentication (OAuth2, JWT), authorization (RBAC, roles), API security, data protection, payment security, and common attack vectors. Use whenever the user wants a security review, penetration test analysis, threat model, or mentions OAuth2…
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
testing-api-authentication-weaknesses
Tests API authentication mechanisms for weaknesses including broken token validation, missing authentication on endpoints, weak password policies, credential stuffing susceptibility, token leakage in URLs or logs, and session management flaws. The tester evaluates JWT implementation, API key handling, OAuth flows, and…