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/write-implementation-plan/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/write-implementation-plan)<a href="https://agentmods.dev/skills/authgear/authgear-server/write-implementation-plan"><img src="https://agentmods.dev/badge/skills/authgear/authgear-server/write-implementation-plan/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/write-implementation-plan"><img src="https://agentmods.dev/badge/skills/authgear/authgear-server/write-implementation-plan.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.00065 | $0.01586 |
| Opus 5.5 | $0.00026 | $0.00634 |
| Sonnet 5.5 | $0.00013 | $0.00317 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
write-implementation-plan 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 29d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Implementation Plan
Write implementation plans as concrete engineering plans, not design notes.
Never assume — ask
If anything needed to write the plan is unknown or uncertain — a behavioral decision the spec doesn't settle, which of two existing patterns to follow, an ambiguous naming/config choice, a tradeoff with no clearly-correct default — stop and ask the user. Do not guess and write the plan around the guess, and do not bury the uncertainty in an "open decisions" section for the user to notice later (the Requirements section below already forbids that). This applies even to small-seeming choices: a wrong assumption made early (e.g. which Redis instance to use, what a field defaults to, whether a check is save-time or runtime) propagates through every section of the plan and is expensive to unwind once implementation has started from it. Ask before writing the section that depends on the answer, not after the plan is done.
Workflow
- Read the current spec, the existing plan, and the relevant code paths before writing the plan.
- Consult related skills to understand implementation conventions:
- Check the
add-go-testskill to understand unit testing patterns and whether the package uses Convey BDD-style tests - Check the
write-e2e-testskill to understand e2e testing requirements and patterns - Check domain-specific skills (e.g.,
update-portal-ui,new-siteadmin-api) if the plan touches those areas
- Check the
- Identify the real integration points in code:
- config types and schema
- runtime entry points
- event and delivery paths
- storage and migration behavior
- tests
- Rewrite the plan around the current spec and the current codebase, not around stale assumptions from an older plan.
Requirements
Write the plan with exact implementation intent.
- Name the exact files to create or modify.
- Name the exact methods, structs, and helpers to add or change.
- Describe the exact method call flow for important runtime paths.
- Separate config-layer types from runtime-layer types.
- Preserve existing codebase conventions for file placement and naming.
- Include backward-compatibility requirements explicitly.
- Include deployment and data-compatibility behavior explicitly when storage keys, payloads, or persisted state are involved.
- Include test coverage requirements.
- Include an atomic commit plan.
What ships with it
1 file 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.
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.
- 29d ago Changed · +30 lines 4b63eaa8cf6c
- 2mo ago First seen · 153 lines · 65 tokens per session scan A 2a86068a86ab
write-implementation-plan is a skill published in the GitHub repository authgear/authgear-server (2,133 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 1,586 once invoked, about $0.0003 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.