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-applicationsgit 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-applications)<a href="https://agentmods.dev/skills/greenpau/caddy-security/configuration-oauth-applications"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-oauth-applications/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-applications"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-oauth-applications.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.03098 |
| Opus 5.5 | $0.00017 | $0.01239 |
| Sonnet 5.5 | $0.00008 | $0.00620 |
| Haiku 4.5 | $0.00004 | $0.00310 |
Grade A, and why
configuration-oauth-applications 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration OAuth Applications
Ownership
oauth application <nickname> belongs inside global security. The Caddy
adapter collects these blocks before parsing other declarations, including
portals and identity providers. caddyfile_oauth_application.go encodes the
header separately from each body statement and delegates to
go-authcrunch/pkg/oidc/parser.NewOAuthApplicationConfigFromDirectives.
Config.AddOAuthApplication validates and copies each registration.
Collect applications directly from the enclosing dispenser: Caddy's
NextSegment omits empty blocks, which otherwise turns an empty registration
into a misleading missing-block error. Dispatch errors must also omit raw
tokens; malformed quoted headers can contain misplaced credentials before the
application parser runs.
Check the closing brace before calling NextBlock: that helper can skip a
brace followed by another token on the same line and read the following setting
inside the application. Reject this form so misplaced consent, PKCE, and
callback settings cannot change the registration.
Reject unquoted closing braces among header/body arguments too. RemainingArgs
accepts them as values, so a missing client_id could otherwise become } and
shift which enclosing block supplies the application's closing brace.
After collection, also require the enclosing security dispenser's nesting
to return to zero, including for direct dispenser callers. Caddy treats
quoted "{" and "}" arguments as literal values. Preserve those values and
following declarations; EOF must still reject an incomplete owned block. Test
missing security/portal delimiters separately from the host global block.
The testcase_security_oauth_applications fixture deliberately uses "{" and
"}" as client display names. These are valid literal values for parser and
provisioning regressions, not recommended operator-facing application names.
The published go-authcrunch module selected in go.mod supports these APIs and
repeated singular redirect_uri statements. No local replacement is required;
follow the dependency workflow
when changing the selected version.
Follow the repository scope
when consulting or selecting sibling source.
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 · 242 lines · 42 tokens per session scan A 4e2a637b7774
configuration-oauth-applications 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 3,098 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.