add-authentication-system

add-authentication-system is a command for coding agents from davepoon/buildwithclaude. It costs 5 tokens per session (687 once invoked), scanned A, original, MIT.

An authentication system implementation plan for identifying users and controlling account access. It covers passwords, third-party sign-in, enterprise single sign-on, tokens, multi-factor authentication, and passwordless methods.

In plain words
What is it for?
It is for planning user registration, profiles, password policies, account verification, role-based access, deactivation, and deletion.
Why use it?
It helps turn security and account requirements into a consistent sign-up, verification, login, and access-control design.

Command

Part of the all-commands plugin — 23 commands shipped together

About the project

davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.

davepoon/buildwithclaude · 3,415 stars · on GitHub · buildwithclaude.com

Install

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.

agentmods
npx agentmods add commands/davepoon/buildwithclaude/add-authentication-system
Clone the repo
git clone --depth 1 https://github.com/davepoon/buildwithclaude

Or install all-commands, the plugin that ships this one along with the rest of its 23 commands.

Wrote 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.

agentmods badge for add-authentication-system

README.md
[![agentmods](https://agentmods.dev/badge/commands/davepoon/buildwithclaude/add-authentication-system.svg)](https://agentmods.dev/commands/davepoon/buildwithclaude/add-authentication-system)
Your own site
<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/add-authentication-system"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/add-authentication-system.svg" alt="Measured on agentmods" height="20"></a>
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 687 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00005 $0.00687
Opus 5 $0.00003 $0.00344
Sonnet 5 $0.00001 $0.00137
Haiku 4.5 $0.00001 $0.00069

Measured today against content hash 97a75b10b9ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

add-authentication-system 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 today.

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.

plugins/all-commands/commands/add-authentication-system.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add Authentication System

Implement secure user authentication system

Instructions

  1. Authentication Strategy Analysis

    • Analyze application requirements and user types
    • Define authentication methods (password, OAuth, SSO, MFA)
    • Assess security requirements and compliance needs
    • Plan user management and role-based access control
    • Evaluate existing authentication infrastructure and integration points
  2. Authentication Method Selection

    • Choose appropriate authentication strategies:
      • Username/Password: Traditional credential-based authentication
      • OAuth 2.0/OpenID Connect: Third-party authentication (Google, GitHub, etc.)
      • SAML: Enterprise single sign-on integration
      • JWT: Stateless token-based authentication
      • Multi-Factor Authentication: SMS, TOTP, hardware tokens
      • Passwordless: Magic links, WebAuthn, biometric authentication
  3. User Management System

    • Set up user registration and account creation workflows
    • Configure user profile management and data storage
    • Implement password policies and security requirements
    • Set up account verification and email confirmation
    • Configure user deactivation and account deletion procedures
  4. Authentication Implementation

    • Implement secure password hashing (bcrypt, Argon2, scrypt)
    • Set up session management and token generation
    • Configure secure cookie handling and CSRF protection
    • Implement authentication middleware and route protection
    • Set up authentication state management (client-side)
  5. Authorization and Access Control

    • Implement role-based access control (RBAC) system
    • Set up permission-based authorization
    • Configure resource-level access controls
    • Implement dynamic authorization and policy engines
    • Set up API endpoint protection and authorization
  6. Multi-Factor Authentication (MFA)

    • Configure TOTP-based authenticator app support
    • Set up SMS-based authentication codes
    • Implement backup codes and recovery mechanisms
    • Configure hardware token support (FIDO2/WebAuthn)
    • Set up MFA enforcement policies and user experience

Read the full file on GitHub · 83 lines

Changes

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.

  1. today First seen · 83 lines · 5 tokens per session scan A 97a75b10b9ae

Subscribe to this mod's changes

add-authentication-system is a command published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 687 once invoked, about $0.0000 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-09-05.