Authgear is an open-source identity and authentication service that provides login, account management, multi-factor authentication, passkeys, and single sign-on for applications. SaaS and mobile-app developers can run it themselves or use Authgear Cloud to manage consumer and enterprise user access. The catalogue entries relate to operating and configuring Authgear's authentication workflows.
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 agentmods add skills/authgear/authgear-server/update-email-templatesnpx skills add authgear/authgear-server --skill update-email-templatesgit clone --depth 1 https://github.com/authgear/authgear-serverWrote 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/authgear/authgear-server/update-email-templates)<a href="https://agentmods.dev/skills/authgear/authgear-server/update-email-templates"><img src="https://agentmods.dev/badge/skills/authgear/authgear-server/update-email-templates.svg" alt="Measured on agentmods" 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.00036 | $0.00677 |
| Opus 5 | $0.00018 | $0.00338 |
| Sonnet 5 | $0.00007 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
update-email-templates 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 6d ago.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Email Templates
Follow this workflow whenever updating email templates.
Scope Rules
- Only edit source template files:
resources/authgear/templates/en/messages/*.txt.gotemplateresources/authgear/templates/en/messages/*.mjml.gotemplate
- Do not edit generated template files directly:
resources/authgear/templates/en/messages/*.txtresources/authgear/templates/en/messages/*.mjml
- In
*.txt.gotemplateand*.mjml.gotemplate, use translations from:resources/authgear/templates/en/messages/translation.json
- Always edit English templates only at source stage.
- Do not manually update non-
enlocales in source-edit commits.
- Do not manually update non-
- Email subject translations are defined in:
resources/authgear/templates/en/translation.json
Workflow
- Edit source templates first:
resources/authgear/templates/en/messages/*.txt.gotemplateresources/authgear/templates/en/messages/*.mjml.gotemplateresources/authgear/templates/en/messages/translation.json(body/content translations)resources/authgear/templates/en/translation.json(subject translations)
- Generate
.mjmlfrom.mjml.gotemplate:go run ./scripts/generatemjml/main.go -i resources/authgear/templates
- Commit source edits and generated
.mjmlin one commit. - Before regenerating non-English translations, delete the changed keys from all non-
enlocale files so the generator knows to recreate them:- For
en/messages/translation.jsonchanges, delete the top-level key (e.g.UsageAlert, notUsageAlert.Alert.Title) from all non-enmessages/translation.jsonfiles:make templates-translation-json-del-key KEY=<TopLevelKey>
- For
en/translation.jsonsubject changes, delete the changed key from all non-entranslation.jsonfiles:make translation-json-del-key KEY=<key>
- Run once per changed top-level key.
- For
- In a separate commit, generate non-English translations:
make -C scripts/python generate-translations- Requires being logged in to Claude:
claude login - If not logged in, stop and ask the user to run
claude loginfirst.
- Finally, generate HTML emails:
make html-email
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.
- 6d ago First seen · 59 lines · 36 tokens per session scan A 050d93d31dcb
update-email-templates is a skill published in the GitHub repository authgear/authgear-server (2,028 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 677 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
auth0-docs
Auth0 — identity platform: auth flows, Universal Login, SSO, identity providers, MFA, RBAC, Actions, tokens.
zeroid
MANUAL TRIGGER ONLY: invoke only when user types /zeroid. Identity infrastructure for AI agents — register identities, issue tokens, delegate to sub-agents, revoke credentials, and manage credential policies via the Zeroid REST API.
zeroid
Identity infrastructure for AI agents — register identities, issue tokens, delegate to sub-agents, revoke credentials, manage policies.
cis-aws-database-2.10
Ensure Database has IAM Auth is Enabled.
auth-oauth
Implements and reviews OAuth 2.0/2.1 flows following RFC 6749, RFC 9700 (BCP), and PKCE (RFC 7636). Use when implementing authorization code flow, token handling, client registration, or securing OAuth endpoints.
schema
Database schema rules for QAuth. Use when working with the identity model, Drizzle ORM, migrations, repositories, or claim resolution. Reflects the CURRENT shipped schema — the identifier-abstraction model (ADR-002, IMPLEMENTED via Epic.