configuration-registrations

configuration-registrations is a skill for Codex from greenpau/caddy-security. It costs 30 tokens per session (1,509 once invoked), scanned A, original, Apache-2.0.

A configuration guide for user sign-up and account enrollment. It covers older approval-based registration and SQLite-backed registration that creates an account after email confirmation.

In plain words
What is it for?
Use it to configure local or SQLite registration, confirmation messages, portal selection, approval handling, and account recovery-related enrollment settings.
Why use it?
It clarifies which identity store and login portal a registration flow uses, and keeps user sign-up separate from OAuth client registration. This helps avoid enabling a registration flow without its required portal or storage.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to configure local or SQLite registration, confirmation messages, portal selection, approval handling, and account recovery-related enrollment settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/greenpau/caddy-security/configuration-registrations
About the project

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.

greenpau/caddy-security · 2,263 stars · on GitHub · authcrunch.com

Install

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.

Any agent
npx skills add greenpau/caddy-security --skill configuration-registrations
Clone the repo
git clone --depth 1 https://github.com/greenpau/caddy-security

Made for: Codex.

Wrote 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.

agentmods badge for configuration-registrations

README.md
[![agentmods](https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-registrations/github.svg)](https://agentmods.dev/skills/greenpau/caddy-security/configuration-registrations)
Your own site
<a href="https://agentmods.dev/skills/greenpau/caddy-security/configuration-registrations"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-registrations/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.

agentmods 80×15 button for configuration-registrations

Your own site · 80×15
<a href="https://agentmods.dev/skills/greenpau/caddy-security/configuration-registrations"><img src="https://agentmods.dev/badge/skills/greenpau/caddy-security/configuration-registrations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,509 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.01509
Opus 5.5 $0.00012 $0.00604
Sonnet 5.5 $0.00006 $0.00302
Haiku 4.5 $0.00003 $0.00151

Measured today against content hash 03e1e70bfd19, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

configuration-registrations 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.

.codex/skills/configuration-registrations/SKILL.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Configuration Registrations

Purpose

Use this skill to configure user signup. Read SQLite enrollment for user registration sqlite <name>: confirmation creates a login account with a fixed policy and requires explicit portal selection. The legacy user registration <name> flow below writes a separate approval dropbox. OAuth client registrations retain their own configuration owner.

Legacy dispatch starts in caddyfile_user.go; registration instructions are collected by caddyfile_user_registration.go. The Caddyfile parser injects name <block-name> and kind local, then forwards the block instructions to authcrunch for validation.

Registration flows attach to the target identity store declared by identity store <name> [<realm>]. During authcrunch validation, portals using that identity store get registration enabled for that store and the registry is attached at runtime. Legacy registrations are selected automatically for eligible portals unless a nonempty explicit enable user registration <name> [<name>...] selection is supplied. The portal must also enable each selected registry's identity store. SQLite workflows require explicit registration selection.

Shape

{
	security {
		user registration signup {
			title "User Registration"
			code {env.REGISTER_CODE}
			dropbox assets/config/registrations_local.json
			require accept terms
			require domain mx
			email provider smtp
			admin email [email protected]
			identity store localdb
			link terms https://example.com/terms
			link privacy https://example.com/privacy
			allow domain example.com
		}

		local identity store localdb {
			realm local
			path assets/config/users.json
		}

		authentication portal myportal {
			enable identity store localdb
		}
	}
}

Required and Defaulted Fields

Authcrunch requires the effective registry config to have name, kind, dropbox, email provider, at least one admin email address, and identity store. In Caddyfile configuration, name comes from the block name and kind local is injected by caddy-security.

Read the full file on GitHub · 168 lines

Files

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.

Changes

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.

  1. today First seen · 168 lines · 30 tokens per session scan A 03e1e70bfd19

Subscribe to this mod's changes

configuration-registrations is a skill published in the GitHub repository greenpau/caddy-security (2,263 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 1,509 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.

Related

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.

MadAppGang/claude-code · 36 tokens

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.

xalgorix/xalgorix · 50 tokens

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.

PramodDutta/qaskills · 46 tokens

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…

kataras/jwt · 107 tokens

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.

26zl/cybersec-toolkit · 44 tokens

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.

glincker/theauth · 67 tokens