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-oauth-providersgit 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-oauth-providers)<a href="https://agentmods.dev/skills/greenpau/caddy-security/configuration-oauth-providers"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-oauth-providers/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-oauth-providers"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-oauth-providers.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.00052 | $0.03082 |
| Opus 5.5 | $0.00021 | $0.01233 |
| Sonnet 5.5 | $0.00010 | $0.00616 |
| Haiku 4.5 | $0.00005 | $0.00308 |
Grade A, and why
configuration-oauth-providers 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration OAuth Providers
Purpose
Use this skill to configure oauth identity provider <name> and named
oauth login store blocks. The
Caddyfile syntax is authoritative in caddyfile_identity.go and
caddyfile_identity_provider_oauth.go; it delegates to the shared upstream
OAuth parser. The provisioning behavior is authoritative in
the module selected by go.mod and any active replacement, especially
pkg/idp/oauth/config.go. A sibling checkout is read-only context and may differ
from that selection; inspect go list -m -json github.com/greenpau/go-authcrunch.
Do not use this skill for sso provider <name> blocks. Those configure the SSO
app/SAML role-assumption feature and belong in configuration-sso-app. Also do
not route saml identity provider <name> blocks here; their headers share the dispatcher
but SAML uses the local go-authcrunch/pkg/idp/saml implementation.
Read shared parsing, grammar compatibility, and trust
when changing OAuth directives, issuer/audience, keys, or parser validation.
Use shared pending-login storage for named
oauth login store declarations, provider namespaces, SQLite capacity, runtime
ownership and callbacks completed by another local Caddy process.
The qualified operator examples include an actual TLS journey using explicit issuer/access-token audience and static Ed25519 keys. Upstream login does not create downstream OP authority. For explicitly selected provider snapshot renewal, see the refresh contract. It reuses captured upstream identity and checks current local attachment/policy; it does not query upstream revocation or exchange upstream refresh credentials. Durable renewal requires root state and explicit file-backed local attachment. Identity-token cookies must be disabled; the callback family uses cookies even when native body refresh is enabled for local login. It also automatically attaches external identities to a private memory store unless a concrete local store is selected. See the current integration boundaries before treating shared-parser support as completed host feature qualification.
What ships with it
3 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 · 323 lines · 52 tokens per session scan A 1c9846ab7a22
configuration-oauth-providers is a skill published in the GitHub repository greenpau/caddy-security (2,263 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 3,082 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…
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…
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.