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 release-and-versioninggit 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/release-and-versioning)<a href="https://agentmods.dev/skills/greenpau/caddy-security/release-and-versioning"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/release-and-versioning/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/release-and-versioning"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/release-and-versioning.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.02122 |
| Opus 5.5 | $0.00017 | $0.00849 |
| Sonnet 5.5 | $0.00008 | $0.00424 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
release-and-versioning 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release and Versioning
Follow the repository scope. Version edits, dependency refreshes, commits, tags, and publication apply only to caddy-security. Read sibling versions/history as inputs; do not bump, sync, fetch into, tag, or release a sibling to unblock this module. Missing upstream releases are separate work. Keep chosen snapshot and report destinations here.
Version Authority
VERSION owns the caddy-security release number. Preserve the existing
1.<minor>.<patch> release line, with no v in the file and v<VERSION> for
the Git tag. A feature change or dependency update alone does not request a
version bump or publication. Read current values from the checkout instead of
copying versions from examples or the sibling repository.
Keep these version surfaces distinct:
MakefilereadsVERSIONintoPLUGIN_VERSION; release recipes read it again for the commit subject and annotated tag.assets/scripts/generate_downloads.shprojectsVERSIONinto README Caddy download URLs. It separately hard-codes thecaddy-traceversion. Verify itsDownload Caddy with the plugins enabledinsertion marker exists before regenerating links, and inspect their placement afterward. The macOS branch requiresgsedas well as BSDsed.go.modselects the go-authcrunch dependency version;../go-authcrunch/VERSIONis the sibling library's release number. Neither sets this module's version.make syncupdates dependency references and removes local replacements; it is a separate dependency refresh, not caddy-security version synchronization.cmd/authcrunch/main.godelegates to Caddy. It has no application version fallback declarations to synchronize. The Makefile does not inject itsPLUGIN_VERSIONwith linker flags, sobin/authcrunch versionalone does not establish this module's release identity.bin/authcrunch security versionreads the linked go-authcrunch module from embedded Go build metadata. It retains pseudo-versions and shows replacements, including(devel)for unversioned local paths. This is dependency identity, distinct from Caddy's version and this repository's release number; see security dependency version.cmd/caddy-authenticator/main.goinitializes*versioned.PackageManagerwith a literal fallback for ordinarygo installbuilds.make buildinjectsVERSIONintomain.appVersion;caddy-authenticator versionprints its banner. GoReleaser builds separate platform archives and injects release/snapshot version, commit and build metadata; see CI and packaging. Keep the fallback synchronized usingmake version-syncafter an explicit VERSION change. Sync validates VERSION first and changes only the existing fallback; it neither bumps the release nor stages files.
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 · 161 lines · 42 tokens per session scan A 05c9bbecfab5
release-and-versioning 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 2,122 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
ship-verification
Post-merge verification pass for Grantex. After any PR merges to main or ships to prod, run this pass without being asked — verify README, Mintlify docs, landing page, SDK READMEs (TS, Python, Go), integration docs, and SEO surfaces are consistent with what just shipped. Use this skill whenever a PR merges, a release…
forge-ship
Enforce a fail-closed release gate across project checks, findings, generated assets, packages, licenses, and installation.
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.
pull-request
Use this whenever the user asks to "open a PR", "ship this", "create the pull request", "make a PR", or once a feature/fix is verified and ready to push. Full lifecycle: branch → commit (commitizen) → issue → draft PR → CI → ready → autonomous monitor loop (fix comments, resolve threads, iterate until CI green + zero…