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/review-prnpx skills add authgear/authgear-server --skill review-prgit 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/review-pr)<a href="https://agentmods.dev/skills/authgear/authgear-server/review-pr"><img src="https://agentmods.dev/badge/skills/authgear/authgear-server/review-pr.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 | $0.00072 | $0.04502 |
| Opus 5 | $0.00036 | $0.02251 |
| Sonnet 5 | $0.00014 | $0.00900 |
| Haiku 4.5 | $0.00007 | $0.00450 |
Grade A, and why
review-pr 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 3d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a code review report for the commits on the current branch that are not yet on the upstream main branch. This skill has three phases: scoping, an initial report, and a mandatory verification pass that re-derives every finding with an objective check (not re-reading the same code and nodding along).
Phase 1: Scope the PR correctly
Do NOT assume the local master/main branch is up to date — in this repo it is frequently stale by hundreds of commits. Establish the true upstream base first:
- Run
git remote -vand identify the canonical upstream remote (the one pointing atauthgear/authgear-server, conventionally namedauthgear; ask the user if ambiguous or absent). git fetch <upstream-remote> main --quietgit merge-base HEAD <upstream-remote>/main— this is the true base, regardless of what localmasterpoints at.git log --oneline <base>..HEADto enumerate exactly the commits in scope. Sanity-check this list againstgit log --oneline -5from the repo status — if the top commits don't match what the user expects, stop and re-check the remote/branch choice before proceeding.git diff --stat <upstream-remote>/main..HEAD— if the stat includes files unrelated to the commit subjects (e.g. translation files, unrelated scripts), that means upstreammainhas advanced independently on other work; this is normal and not part of the PR. Don't let it inflate the reported scope — cross-check withgit show --stat <commit>for each commit in step 4 individually to get the true per-commit file list.
Phase 2: Write the report
Structure the report under these six headings. Base every claim on an actual diff read (git show <commit>, git diff <base>..HEAD -- <path>), not on commit message text alone — commit messages describe intent, not necessarily what the code does.
-
Major purpose — 3-6 sentences synthesizing what the set of commits accomplishes and why, grouped by theme if the commits span multiple concerns.
-
API interface changes — enumerate concretely:
- GraphQL: new/changed types, fields, args in
schema.graphqland the resolver file that backs them (pkg/admin/graphql/,pkg/portal/graphql/) - Go: new/changed exported struct fields, function signatures in
pkg/lib/ - HTTP/config: new endpoints, changed request/response shapes,
authgear.yamlschema changes - Note whether each change is additive (safe) or a rename/removal (breaking)
- GraphQL: new/changed types, fields, args in
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.
- 3d ago Changed · +9 lines 46937f004e39
- 5d ago First seen · 92 lines · 72 tokens per session scan A 9fd8c60f1998
review-pr is a skill published in the GitHub repository authgear/authgear-server (2,024 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 4,502 once invoked, about $0.0004 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.