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.
Borrowing it
Nothing to install: this file belongs to greenpau/caddy-security. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/greenpau/caddy-security/main/AGENTS.mdgit 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/instructions/greenpau/caddy-security/agents-md)<a href="https://agentmods.dev/instructions/greenpau/caddy-security/agents-md"><img src="https://agentmods.dev/badge/instructions/greenpau/caddy-security/agents-md/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/instructions/greenpau/caddy-security/agents-md"><img src="https://agentmods.dev/badge/instructions/greenpau/caddy-security/agents-md.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.03238 | $0.03238 |
| Opus 5.5 | $0.01295 | $0.01295 |
| Sonnet 5.5 | $0.00648 | $0.00648 |
| Haiku 4.5 | $0.00324 | $0.00324 |
Grade A, and why
caddy-security AGENTS.md 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Summary
caddy-security is a Go module that provides a Caddy v2 security app and
HTTP authentication/authorization integrations backed by
github.com/greenpau/go-authcrunch. The global security Caddyfile option is
adapted into the app configuration and can define credentials, messaging,
identity stores, OAuth and SAML identity providers, SSO app providers, local
users, registration flows, authentication portals, authorization policies, and
pluggable secrets managers.
The module registers two primary HTTP integrations: authenticate, which serves
an authentication portal for form-based, basic, local, LDAP, OpenID Connect,
OAuth 2.0, and SAML authentication; and authorize, which applies gatekeeper
policies to JWT/PASETO claims and direct OAuth sessions. The legacy authorization
provider remains available for Caddy's authentication provider chain.
In Caddy terms, security is an application: a top-level Caddy module with its
own lifecycle, configuration, provisioning, and shared runtime state. The
authenticate and authorize directives are Caddy plugins: HTTP-facing modules
that attach to routes and delegate to the provisioned security app. The app
owns reusable authcrunch configuration such as portals, gatekeepers, identity
stores, credentials, messaging, and secrets managers; the plugins apply that
configuration to individual requests in the HTTP handler/authentication chain.
The security app can also load external plugins of its own, especially under
the security.secrets namespace, such as
github.com/greenpau/caddy-security-secrets-static-secrets-manager and
github.com/greenpau/caddy-security-secrets-aws-secrets-manager.
Repository Scope
Keep all repository changes inside caddy-security. Sibling repositories,
including ../go-authcrunch, are read-only references and are updated
separately. Do not edit their files or Git state, run their build/test/maintenance
commands, or write generated output into them.
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 · 257 lines · 3,238 tokens per session scan A 703af85dee51
caddy-security AGENTS.md is an instructions file published in the GitHub repository greenpau/caddy-security (2,263 stars, last pushed today), licensed Apache-2.0. It adds 3,238 tokens to every session, about $0.0130 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.