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 configuration-authenticationgit 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/configuration-authentication)<a href="https://agentmods.dev/skills/greenpau/caddy-security/configuration-authentication"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-authentication/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/configuration-authentication"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-authentication.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.00042 | $0.02304 |
| Opus 5.5 | $0.00017 | $0.00922 |
| Sonnet 5.5 | $0.00008 | $0.00461 |
| Haiku 4.5 | $0.00004 | $0.00230 |
Grade A, and why
configuration-authentication 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration Authentication
Purpose
Use this skill to configure authentication portal <name> blocks and the
route-level authenticate with <portal> handler.
Use configuration-http-integrations to place portal routes, select matchers, wire same-host or split-host portals, separate portal/protected routes, and check directive ordering.
Read these files when details matter:
caddyfile_authn.gofor the portal block.caddyfile_authn_token_refresh.goand token refresh for readable portal refresh configuration, explicit eligible realms, transports, bounded lifetimes and stores, cookies, placeholders and TLS validation. Read named refresh storage for explicit SQLite selection, private file ownership, root-state generations and commit recovery.caddyfile_authn_documents.goand Documents configuration for flat API directives, explicit local realms, private storage, quotas, runtime values and permanent origin/mount bindings.caddyfile_authn_crypto.gofor crypto key directives.caddyfile_authn_misc.goforenable,validate, andtrust.caddyfile_authn_admin_api.goand selected upstreampkg/authn/admin_api/parserfor the independent admin/API key-export switches.plugin_authn.gofor route-levelauthenticatesyntax.../go-authcrunch/config.gofor portal validation, default backend attachment, and user registration wiring.../go-authcrunch/pkg/authn/config.goand../go-authcrunch/pkg/authn/portal.gofor portal defaults and runtime behavior.
Use focused repo-local skills for specialized portal sub-blocks:
- Use configuration-authentication-cross-device to enable QR/link login, explicit approval, browser binding, cancellation and volatile request lifecycle through the existing portal route.
- Use configuration-oauth-applications
to configure portal
oidc providerblocks, named client selection, private registrations, and dedicated provider signing keys. Its provider reference covers explicit realm participation and separate issuers/cookie scopes across portals; attaching a store for portal login does not enable its realm for OIDC. - Use configuration-crypto to configure
portal
cryptodefaults, JWT signing keys, auto-generated keys, token names and lifetimes, secret-backed key material, System APIsystemkeys, and explicitly selectedaccess signerandaccess token profilesettings. - Use configuration-authentication-cookies
to configure
cookiedirectives and token-cookie naming. - Use configuration-authentication-ui
to configure
uiblocks, templates, static assets, custom CSS/JS/HTML, themes, languages, logos, and private links. - Use configuration-authentication-user-transforms
to configure
transform userblocks, ACL matchers, typed claims, conditional challenge selection, additive legacy requirements, claim replacements, and transform UI links. Persisted local-user challenge rules belong to configuration-users. - Use configuration-ticket-providers to enable trusted application ticket login and its browser-binding provider.
- Use configuration-saml-providers
to configure
saml identity provider <name>login providers enabled by the portal. - Use authentication-portal-api to build
or troubleshoot JSON login,
/whoami,/beacon, refresh token, Documents, and admin/server API interactions.
What ships with it
5 files 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 · 224 lines · 42 tokens per session scan A f98e40ec6019
configuration-authentication is a skill published in the GitHub repository greenpau/caddy-security (2,263 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 2,304 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.
implementing-jwt-signing-and-verification
JSON Web Tokens (JWT) defined in RFC 7519 are compact, URL-safe tokens used for authentication and authorization in web applications. This skill covers implementing secure JWT signing with HMAC-SHA256.
API Security Testing
Comprehensive API security testing based on OWASP API Security Top 10 including broken authentication, injection attacks, rate limiting, BOLA/BFLA vulnerabilities, and automated security scanning with ZAP and custom scripts.
jwt
Development guide for the jwt JSON Web Token library for Go (github.com/kataras/jwt). Use this skill when signing or verifying JWTs, choosing a signing algorithm (HMAC, RSA, RSA-PSS, ECDSA, EdDSA), reading or validating standard or custom claims, setting expiry and clock-skew tolerance, rotating keys with a kid-based…
configuring-oauth2-authorization-flow
Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. This skill covers flow selection, PKCE implementation, token.
theauth
Install and use theAuth (@glinr/theauth), the TypeScript auth SDK for AI agents and humans. Use when adding agent identity, scoped permissions, delegation, audit logs, human sign-in plugins, or an MCP OAuth 2.1 authorization server to a Node, Bun, Deno or edge project.