Reading Mailcatcher API
bitwarden/ai-plugins
Retrieves a link from Mailcatcher. An agent skill from bitwarden/ai-plugins.
Configure email and file messaging providers, SMTP transport, sender/authentication, templates, and registration delivery wiring.
Install Configuration Messaging
$ npx skills add greenpau/caddy-security --skill configuration-messaging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install greenpau/caddy-security configuration-messaging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/greenpau/caddy-security.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/configuration-messaging .claude/skills/configuration-messaging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "configuration-messaging" agent skill from https://github.com/greenpau/caddy-security/tree/main/.codex/skills/configuration-messaging into .claude/skills/configuration-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuration-messaging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/greenpau/caddy-security/tree/main/.codex/skills/configuration-messagingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add greenpau/caddy-security --skill configuration-messaging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install greenpau/caddy-security configuration-messaging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/greenpau/caddy-security.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/configuration-messaging .agents/skills/configuration-messaging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "configuration-messaging" agent skill from https://github.com/greenpau/caddy-security/tree/main/.codex/skills/configuration-messaging into .agents/skills/configuration-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuration-messaging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add greenpau/caddy-security --skill configuration-messaging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install greenpau/caddy-security configuration-messaging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/greenpau/caddy-security.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/configuration-messaging .cursor/skills/configuration-messaging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "configuration-messaging" agent skill from https://github.com/greenpau/caddy-security/tree/main/.codex/skills/configuration-messaging into .cursor/skills/configuration-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuration-messaging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/greenpau/caddy-security.git --path .codex/skills/configuration-messaging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add greenpau/caddy-security --skill configuration-messaging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install greenpau/caddy-security configuration-messaging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/greenpau/caddy-security.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/configuration-messaging .gemini/skills/configuration-messaging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "configuration-messaging" agent skill from https://github.com/greenpau/caddy-security/tree/main/.codex/skills/configuration-messaging into .gemini/skills/configuration-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuration-messaging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install greenpau/caddy-security configuration-messagingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add greenpau/caddy-security --skill configuration-messaging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/greenpau/caddy-security.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/configuration-messaging .github/skills/configuration-messaging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "configuration-messaging" agent skill from https://github.com/greenpau/caddy-security/tree/main/.codex/skills/configuration-messaging into .github/skills/configuration-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuration-messaging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add greenpau/caddy-security --skill configuration-messaging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install greenpau/caddy-security configuration-messaging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/greenpau/caddy-security.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/configuration-messaging .opencode/skills/configuration-messaging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "configuration-messaging" agent skill from https://github.com/greenpau/caddy-security/tree/main/.codex/skills/configuration-messaging into .opencode/skills/configuration-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuration-messaging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
configuration-messaging- GitHub stars
- 2.3k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 600 words
- Files
- 2
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Configure email and file messaging providers, SMTP transport, sender/authentication, templates, and registration delivery wiring.
- Distinguish parsed settings from actual delivery behavior
- SKILL.md covers Purpose, Email Provider, File Provider and Template Directive, plus 2 more sections
- Reaches github.com
- Tasks that involve Transactional email
What it does
Configuration Messaging is an agent skill from greenpau/caddy-security. Configure email and file messaging providers, SMTP transport, sender/authentication, templates, and registration delivery wiring. Use to distinguish parsed settings from actual delivery behavior.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Backend & APIs, covering Transactional email and Authentication. The repository describes itself as: 🔐 Authentication, Authorization, and Accounting (AAA) App and Plugin for Caddy v2. 💎 Implements Form-Based, Basic, Local, LDAP, OpenID Connect, OAuth 2.0 (Github, Google…. The licence is Apache-2.0.
When your agent uses it
- Distinguish parsed settings from actual delivery behavior
- Tasks that involve Transactional email
- Tasks that involve Authentication
Example prompts
- “/configuration-messaging”
What it can do on your machine
Read from SKILL.md and the folder at commit a48553d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are caddyfile).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Configuration Messaging loads about 1.6k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 600 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from greenpau/caddy-security at commit a48553d, republished under its Apache-2.0 licence (© greenpau). 600 words, ~1,606 tokens.
Download SKILL.mdSave it as
.claude/skills/configuration-messaging/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- configuration-messaging
- description
- Configure email and file messaging providers, SMTP transport, sender/authentication, templates, and registration delivery wiring. Use to distinguish parsed settings from actual delivery behavior.
Configuration Messaging
Purpose
Use this skill to configure messaging <kind> provider <name> blocks. The
parser is caddyfile_messaging.go.
Messaging is most often needed by registration flows, password recovery, MFA OTP, or administrative notifications.
caddyfile_messaging.go forwards provider subdirectives directly to
go-authcrunch/pkg/messaging. Use the authcrunch instruction names exactly;
for example, file providers use root_dir, not rootdir.
Email Provider
{
security {
messaging email provider localhost-smtp-server {
address 127.0.0.1:1025
protocol smtp
credentials smtp_root
sender root@example.com "Example Auth Portal"
bcc admin@example.com audit@example.com
template password_recovery templates/password_recovery.tmpl
template registration_confirmation templates/registration_confirmation.tmpl
template registration_ready templates/registration_ready.tmpl
template registration_verdict templates/registration_verdict.tmpl
template mfa_otp templates/mfa_otp.tmpl
}
}
}Email providers require:
address <host:port>.protocol smtporprotocol smtps.- Exactly one of
credentials <name>orpasswordless. sender <email> [display_name].
Use passwordless instead of credentials <name> when the SMTP server does
not require authentication.
In selected go-authcrunch v1.3.4, smtp opens a plaintext SMTP connection;
the sender does not negotiate STARTTLS. smtps uses implicit TLS with
certificate verification. A server requiring STARTTLS is not supported by
switching protocol smtp to port 587. Use an endpoint that supports the chosen
transport; there is no Caddyfile STARTTLS or custom SMTP CA directive here.
The referenced credentials <name> object follows
configuration-credentials.
For local registration message checks, use the built-in file provider below
with a disposable root_dir under this checkout's tmp/; no SMTP tool install
is needed. This verifies rendered content, not SMTP authentication, TLS or
recipient delivery. When the task requires SMTP evidence, use an explicitly
configured loopback test server and synthetic credentials, inspect its envelope
recipients as well as message headers, and stop it after the check. Keep any
added test tooling and its output in the repository and pin its version.
File Provider
messaging file provider local_outbox {
root_dir tmp/registration-messages
sender root@example.com "Example Auth Portal"
template registration_confirmation templates/registration_confirmation.tmpl
template registration_ready templates/registration_ready.tmpl
template registration_verdict templates/registration_verdict.tmpl
}File providers write .eml messages under root_dir. Authcrunch requires both
root_dir <path> and sender <email> [display_name]. File providers do not use
credentials or passwordless.
In v1.3.4, email providers put bcc <email>... into a Bcc message header but
do not add those addresses to SMTP RCPT TO. Do not rely on it for copy
delivery or recipient privacy: recipients can see that header. This is an
upstream sender limitation, not configurable Caddy behavior. File providers
parse and preserve bcc, but the file sender writes only To; it also omits
the configured sender from the .eml content.
Both email and file providers validate and preserve these template IDs:
password_recovery.registration_confirmation.registration_ready.registration_verdict.mfa_otp.
Show full SKILL.md (253 more words)Show less
Template Directive
Use template <id> <path> to add an entry to the provider's templates map.
Authcrunch validates the ID and preserves the path, but the provider parser does
not check that the path exists.
Current registration notification rendering does not load provider template
paths. It uses embedded English subject/body templates from the sibling
go-authcrunch repository, then sends the rendered message through the
configured provider.
Default messaging template files live under:
https://github.com/greenpau/go-authcrunch/tree/main/pkg/messaging/email_templates/en
The embedded asset loader strips email_templates/ and .template, so
registration_confirmation_subject.template is looked up as
en/registration_confirmation_subject.
Default files by validated template ID:
registration_confirmation:registration_confirmation_subject.templateandregistration_confirmation_body.template.registration_ready:registration_ready_subject.templateandregistration_ready_body.template.registration_verdict:registration_verdict_subject.templateandregistration_verdict_body.template.password_recovery: no default messaging subject/body file inpkg/messaging/email_templates; password recovery UI lives in the portal sandbox template, not in the messaging template library.mfa_otp: no default messaging subject/body file inpkg/messaging/email_templates.
Registration Wiring
Registration flows reference messaging providers by name with the historical
email provider <name> directive. The referenced provider may be either kind;
authcrunch resolves whether it is an email or file messaging provider at
send time.
user registration signup {
email provider localhost-smtp-server
admin email admin@example.com
}The registration block belongs to configuration-registrations.
Fixtures
Use these examples:
caddyfile_messaging_test.go.testdata/caddyfile_adapt/testcase_authenticate_with_registration.Caddyfile.
The parser test checks encoded instructions. Adapt/resolution and lifecycle
tests verify configuration and replacement, not message delivery. This checkout
has no complete user-registration SMTP E2E. Acceptance for a sender change
needs a disposable recipient server that observes the negotiated transport,
authentication, envelope recipients and rendered confirmation link; a Bcc
header alone is not delivery evidence. File-provider acceptance checks private
.eml output and content, and reports SMTP behavior as untested.
© greenpau, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .codex/skills/configuration-messaging of greenpau/caddy-security.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit a48553d
Compare with similar skills
Configuration Messaging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Configuration Messaging this skillgreenpau/caddy-security | 2.3k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Reading Mailcatcher APIbitwarden/ai-plugins | 154 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Email Systemgjovanovicst/golang-auth-api | 130 | — | ~1.7k | Automated safety check: Pass | MIT | |
| ResendLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.1k | Automated safety check: Pass | MIT | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Supabase Development and Debuggingsupabase/agent-skills | 2.7k | 3 repos | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
Email System
gjovanovicst/golang-auth-api
Complete documentation of the email subsystem including template resolution, variable pipeline, rendering engines, SMTP config, and default templates.
Resend
LeoYeAI/openclaw-master-skills
Resend API integration with managed authentication. An agent skill from LeoYeAI/openclaw-master-skills.
Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
- Official
Supabase Development and Debugging
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
Better Auth Best Practices
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
More from greenpau/caddy-security
All 29 skills in this repoAuthentication Portal API
greenpau/caddy-security
Build or troubleshoot portal JSON/native login clients, refresh, profile and admin APIs, and public JWKS.
Coding Directives
greenpau/caddy-security
Implement or review caddy-security Go code, Caddy modules, parsers, lifecycle, and HTTP delegation.
Configuration
greenpau/caddy-security
Build or review caddy-security Caddyfiles and select focused configuration skills.
Configuration Crypto
greenpau/caddy-security
Configure portal/policy JWT keys, token names and lifetimes, key loading and generation, public-key discovery, and System API encryption keys.
Configuration HTTP Integrations
greenpau/caddy-security
Mount authenticate and authorize handlers, separate portal and protected routes, align auth URLs, and preserve trusted proxy metadata.
Configuration State
greenpau/caddy-security
Configure durable AuthCrunch runtime state, exclusive storage ownership, stop/start persistence, reload rejection, and recovery.
Related
Categories
Questions about Configuration Messaging
What does Configuration Messaging do?
Configure email and file messaging providers, SMTP transport, sender/authentication, templates, and registration delivery wiring. Configuration Messaging is an agent skill from greenpau/caddy-security. Configure email and file messaging providers, SMTP transport, sender/authentication, templates, and registration delivery wiring.
When should I use Configuration Messaging?
Configuration Messaging fits situations like: distinguish parsed settings from actual delivery behavior; tasks that involve Transactional email; tasks that involve Authentication.
How do I install Configuration Messaging in Claude Code?
Run `npx skills add greenpau/caddy-security --skill configuration-messaging -a claude-code`. Or copy the skill folder (.codex/skills/configuration-messaging in greenpau/caddy-security) into .claude/skills/configuration-messaging in your project. Claude Code loads it when a task matches its description.
How do I install Configuration Messaging in Codex?
Run `npx skills add greenpau/caddy-security --skill configuration-messaging -a codex`. Or copy the skill folder (.codex/skills/configuration-messaging in greenpau/caddy-security) into .agents/skills/configuration-messaging in your project. Codex loads it when a task matches its description.
Can I use Configuration Messaging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add greenpau/caddy-security --skill configuration-messaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/configuration-messaging, .gemini/skills/configuration-messaging, .github/skills/configuration-messaging and .opencode/skills/configuration-messaging in your project.
What does Configuration Messaging need to run?
SKILL.md names no scripts, command-line tools or credentials: Configuration Messaging is instructions for the agent only.
Does Configuration Messaging access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Configuration Messaging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Configuration Messaging use?
Configuration Messaging is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Configuration Messaging use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Configuration Messaging?
Skills that share tags, products or a category with Configuration Messaging: Reading Mailcatcher API (bitwarden/ai-plugins, 154 stars), Email System (gjovanovicst/golang-auth-api, 130 stars), Resend (LeoYeAI/openclaw-master-skills, 2.2k stars) and Fortify Development (coollabsio/coolify, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Configuration Messaging?
greenpau (a GitHub user) maintains it in greenpau/caddy-security, which has 2,252 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 5, 2026.
Source: greenpau/caddy-security on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.