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.
Borrowing it
Nothing to install: this file belongs to authgear/authgear-server. 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/authgear/authgear-server/main/.claude/skills/add-portal-screen/SKILL.mdgit 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/add-portal-screen)<a href="https://agentmods.dev/skills/authgear/authgear-server/add-portal-screen"><img src="https://agentmods.dev/badge/skills/authgear/authgear-server/add-portal-screen/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/skills/authgear/authgear-server/add-portal-screen"><img src="https://agentmods.dev/badge/skills/authgear/authgear-server/add-portal-screen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.03301 |
| Opus 5.5 | $0.00014 | $0.01320 |
| Sonnet 5.5 | $0.00007 | $0.00660 |
| Haiku 4.5 | $0.00003 | $0.00330 |
Grade A, and why
add-portal-screen 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 yesterday.
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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow this guide when adding screens or components to the portal.
Step 1: Locate existing patterns
Before writing any code, read at least one existing screen from portal/src/screens/ that is similar to the feature being built. Reading the full file is preferred so you understand the complete pattern.
Good reference screens:
- Config-form screen with tabs:
portal/src/screens/fraud-protection/FraudProtectionConfigurationScreen.tsx - Screen with sub-tab files:
portal/src/screens/api-resources/APIResourceDetailsScreen.tsx
Also read any components under portal/src/components/ in the same feature area that exist already.
Step 2: File structure
Screens
New screens go in:
portal/src/screens/<feature-name>/
<FeatureName>Screen.tsx
<FeatureName>Screen.module.css
- Use kebab-case for the directory name (e.g.,
fraud-protection,api-resources). - Use PascalCase for file names (e.g.,
FraudProtectionConfigurationScreen.tsx). - Sub-tabs of a screen that are complex enough to deserve their own file live in the same screen directory, not in
components/.
Components
Reusable or extracted sub-components go in:
portal/src/components/<feature-name>/
<ComponentName>.tsx
<ComponentName>.module.css
- A component that is only used by one screen is still placed in
components/when it is large enough to deserve its own file. - Shared low-level UI primitives (buttons, inputs, etc.) go in
portal/src/components/common/.
CSS modules
Every component or screen that has its own styles gets its own .module.css file. Name it identically to the .tsx file (e.g., FraudProtectionOverviewTab.module.css).
When two sibling components share many CSS classes (e.g., two card variants), they may both import from a single shared .module.css file. Name it after the dominant component (e.g., OverviewMetricCard.module.css shared by OverviewMetricCard.tsx and OverviewEnforcementCard.tsx).
Step 3: Screen anatomy
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.
- yesterday Changed · +11 lines 4d1adcbfa99f
- 2mo ago First seen · 386 lines · 34 tokens per session scan A 54a744f9fcaf
add-portal-screen is a skill published in the GitHub repository authgear/authgear-server (2,133 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 3,301 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-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.
configuring-multi-factor-authentication-with-duo
Deploy Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points. This skill covers Duo integration methods, adaptive authentication policies, device trust.
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.