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-http-integrationsgit 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-http-integrations)<a href="https://agentmods.dev/skills/greenpau/caddy-security/configuration-http-integrations"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-http-integrations/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-http-integrations"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-http-integrations.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.00043 | $0.03076 |
| Opus 5.5 | $0.00017 | $0.01230 |
| Sonnet 5.5 | $0.00009 | $0.00615 |
| Haiku 4.5 | $0.00004 | $0.00308 |
Grade A, and why
configuration-http-integrations 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration HTTP Integrations
Purpose
Use this skill to wire caddy-security's route-level HTTP integrations:
authenticate [<matcher>] with <portal> [at <mount>] and
authorize [<matcher>] with <policy>.
The security app defines authentication portals and authorization policies;
the HTTP integrations attach those configured objects to Caddy routes.
Portal internals belong to configuration-authentication;
policy internals belong to configuration-authorization.
Route mounting does not require reloading either owner unless its configuration
also needs changes.
Prefer names that reveal the referenced object type in generated examples, such
as myportal or local_portal for portals and app_policy or local_policy
for policies. Policy names are not required to end in _policy, but the suffix
makes authorize with <policy> intent clear.
Use authentication portal myportal with authenticate with myportal at /auth, or choose
a descriptive portal name. Avoid authentication portal portal in examples,
fixtures, and tests; the repeated word obscures the declaration's name.
Read these files when details matter:
plugin_authn.goforauthenticatesyntax and directive order.plugin_authz.goforauthorizesyntax and directive order.assets/config/Caddyfile,assets/config/home.Caddyfile, andassets/config/multiportal.Caddyfilefor current route shapes.testdata/caddyfile_adapt/testcase_authenticate_ok.Caddyfile,testdata/caddyfile_adapt/testcase_authenticate_explicit_mounts.Caddyfile,testdata/caddyfile_adapt/testcase_authorize_ok.Caddyfile, andtestdata/caddyfile_adapt/testcase_authenticate_with_registration.Caddyfilefor focused adapt fixtures.
Caddy Host Defaults
Cross-device login uses the existing portal handler for its entire mount-relative
/cross-device namespace. Preserve the prefix and library strict-origin
Referrer-Policy; no extra handler or CORS layer is needed. Provider realms named
cross-device retain their own namespace. Use
configuration-authentication-cross-device
to review transfer paths, HTTPS/Origin boundaries and root/nested mount tests.
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 · 326 lines · 43 tokens per session scan A 3d2397c49ce4
configuration-http-integrations is a skill published in the GitHub repository greenpau/caddy-security (2,263 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 3,076 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.