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-cryptogit 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-crypto)<a href="https://agentmods.dev/skills/greenpau/caddy-security/configuration-crypto"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-crypto/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-crypto"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-crypto.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.00037 | $0.03740 |
| Opus 5.5 | $0.00015 | $0.01496 |
| Sonnet 5.5 | $0.00007 | $0.00748 |
| Haiku 4.5 | $0.00004 | $0.00374 |
Grade A, and why
configuration-crypto 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration Crypto
Purpose
Use this skill for global access signer declarations, portal signer selection,
portal/policy access token profile blocks, and their existing crypto directives.
Surrounding declarations belong to
configuration-authentication and
configuration-authorization.
runtime resolution and
secrets own replacement semantics and manager
configuration; this skill owns how the resulting key material is used.
Read these files when details matter:
caddyfile_authn_crypto.goandcaddyfile_authz_crypto.gofor the thin Caddyfile parser wrappers.caddyfile_resolve.gofor env, file, and secrets substitution in raw crypto lines before authcrunch validation.../go-authcrunch/pkg/kms/for the real crypto grammar, key loading, defaults, signing, verification, and System API keys.../go-authcrunch/pkg/authn/config.goandportal.gofor portal key-store construction, token signing, and the portal validator.../go-authcrunch/pkg/authz/config.go,gatekeeper.go, andpkg/authz/validator/for policy key-store construction, token discovery, and verification.../go-authcrunch/pkg/authproxy/andpkg/system/for remote Basic/API-key auth encrypted withsystemkeys.
Mental Model
The caddy-security parser only checks that a crypto line has at least three
arguments and begins with key or default. It then stores the full line as
raw encoded authcrunch KMS config. The deeper syntax is validated later by
go-authcrunch/pkg/kms.
During provisioning, caddy-security resolves placeholders and secrets inside
raw crypto lines, overwrites the raw entries, and calls authcrunch Validate.
That builds CryptoKeyStoreConfig; runtime then builds a CryptoKeyStore from
that config.
If no explicit crypto key ... lines exist, authcrunch auto-generates an ES512
sign-verify key by default; other algorithms are described below. This is
volatile by default. Explicit keys provide stable material across independent
instances; optional persistent state can retain
generated material across an exclusive owner's stop/start. Key persistence alone
does not share session state or authorize concurrent owners.
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 · 351 lines · 37 tokens per session scan A b6d30b65ec7b
configuration-crypto is a skill published in the GitHub repository greenpau/caddy-security (2,263 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 3,740 once invoked, about $0.0001 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.