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-stategit 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-state)<a href="https://agentmods.dev/skills/greenpau/caddy-security/configuration-state"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-state/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-state"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-state.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.00035 | $0.01695 |
| Opus 5.5 | $0.00014 | $0.00678 |
| Sonnet 5.5 | $0.00007 | $0.00339 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
configuration-state 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persistent Runtime State
Use this skill for security { state { ... } }, native config.state JSON,
restart persistence, and its lifecycle boundary. OAuth client registrations and
identity databases retain their existing owners. Keep changes and test output
in this repository; sibling AuthCrunch source is a read-only reference under
the repository scope.
Configuration
Add one optional block inside the global security app:
{
security {
state {
directory /var/lib/authcrunch/runtime
}
# Existing providers, portals and/or authorization policies follow.
}
}
This is a fragment: a usable security app also needs a portal or policy.
The JSON field is apps.security.config.state, with the library's shape:
"state":{"directory":"/var/lib/authcrunch/runtime"}.
Paths must be absolute, non-root and private. Quote spaces. Omission retains
volatile behavior; an empty block, duplicate block/setting, extra arguments,
unknown settings and nested blocks are errors. Closing braces end their lines.
Use {$VARIABLE} for adaptation-time substitution. {env.VARIABLE} and whole
secrets:manager:key references remain declarative until provisioning; an empty
or invalid resolved directory fails instead of disabling persistence.
caddyfile_state.go owns traversal and cfgutil.EncodeArgs encoding;
go-authcrunch/pkg/state/parser.NewStateConfigFromDirectives owns grammar and
normalization. Deferred values use a validation-only stand-in, retain their
original token in Config.State, and are resolved/revalidated in the private
configuration copy. Never open the stand-in, choose a process-specific directory,
implement another directory grammar, or copy the library's records, encryption,
session DTOs, replay history or locks into Caddy.
Lifecycle and operation
Pending cross-device interactions are always volatile. Reload or complete stop/start discards them even when completed sessions use persistent state. The existing rejection of overlapping persistent reload still applies. See cross-device lifecycle.
What ships with it
2 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 · 151 lines · 35 tokens per session scan A 8525ea3a85b3
configuration-state is a skill published in the GitHub repository greenpau/caddy-security (2,263 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 1,695 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.