Token导航 LogoToken导航

Agent Skill · 开发

account-security(账户安全)

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

account-security 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 17,066。

总安装 445周安装 18GitHub Stars 19下载 140核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:account-security(账户安全)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/account-security
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill account-security
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill account-security

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于辅助安全审计、权限检查和认证流程分析,适合梳理敏感配置与排查常见漏洞。适用于账户系统构建、现有系统安全审计及凭证泄露防护场景。通过 GitHub 安装,在 Codex、Claude、Cursor、Gemini CLI 中调用。涉及密钥或生产数据时需确认最小权限与脱敏方式,不可直接依赖工具输出结论。

account-security 属于开发类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/account-security

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill acc…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

account-security 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill account-secur…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

account-security 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

account-security 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

account-security 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

account-security 用的人多吗?

公开数据是累计安装 445 次,近一周安装 18 次,下载 140 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

account-security 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
account-security

账户安全 · 本页

44519需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Account Security

Overview

Customer accounts hold saved payment methods, loyalty points, purchase history, and shipping addresses — making them high-value targets for credential-stuffing attacks and account takeovers. Effective account security layers brute-force protection on the login page, breach-exposed password detection, optional multi-factor authentication (MFA), and anomaly detection for account takeover patterns. The right approach depends heavily on your platform — Shopify manages most security controls at the platform level, while WooCommerce requires additional plugins.

When to Use This Skill

  • When building a customer account system from scratch
  • When auditing an existing account system for security weaknesses
  • When observing credential stuffing attacks (high login failure rates from distributed IPs)
  • When adding MFA as an optional or required layer for high-value customers
  • When implementing "Sign in with Google/Apple" as a more secure alternative to passwords

Core Instructions

Step 1: Understand your platform's security model

PlatformWhat the Platform HandlesWhat You Need to Configure
ShopifySSL/TLS, brute-force protection on login, PCI compliance, server-side securityCustomer account settings, whether to require phone verification, Social login apps for Google/Apple sign-in
WooCommerceBasic login form onlyInstall Wordfence (free) for brute-force protection, limit login attempts, 2FA, and login security monitoring
BigCommerceSSL/TLS, platform-managed account security, basic brute-force protectionTwo-factor authentication for admin users; customer-facing 2FA requires an app
Custom / HeadlessNothing — you build all security controlsRate limiting, password hashing, MFA, session management, ATO detection

Step 2: Platform-specific account security setup


Shopify

Shopify handles the majority of customer account security at the platform level — you do not manage SSL, brute-force detection, or password hashing yourself.

Enable new customer accounts (passwordless login): Shopify offers two account experiences:

  1. Go to Settings → Customer accounts
  2. New customer accounts (recommended): customers log in with a one-time 6-digit code sent to their email or phone; no password to steal or brute-force
  3. Classic customer accounts: traditional email/password accounts

Switching to new customer accounts (passwordless) eliminates the most common attack vectors: credential stuffing and brute force.

Two-step verification for admin accounts:

  1. Go to Settings → Users and permissions
  2. Click on a user → enable Two-step authentication required
  3. Shopify supports authenticator apps (TOTP) and SMS for admin 2FA

Social login (Google/Facebook/Apple): Install a social login app from the Shopify App Store:

  • Oxi Social Login — supports Google, Facebook, Apple, LinkedIn
  • NDNAPPS Social Login — supports Google, Facebook, Apple These apps add social login buttons to the account creation and login pages.

Detecting suspicious customer activity: Shopify does not expose customer login events for programmatic monitoring. For advanced monitoring, use Shopify's Fraud analysis in orders to detect account takeovers combined with fraudulent purchases.


WooCommerce

WooCommerce's built-in login form has no rate limiting, MFA, or advanced security. You must add these via plugins.

Install Wordfence Security (free, recommended):

  1. Install and activate Wordfence Security from the WordPress plugin directory
  2. Go to Wordfence → Login Security
  3. Enable Brute Force Protection:

- Lock out after X failed attempts (default: 20) - Lock out duration (default: 4 hours) - Count failures over X minutes (default: 5 minutes)

  1. Enable Two-Factor Authentication for admin users (Wordfence supports authenticator app TOTP)

Limit Login Attempts Reloaded (free alternative for just rate limiting):

  1. Install Limit Login Attempts Reloaded
  2. Configure: lockout after 4 failures, lock for 20 minutes, notify by email after 4 lockouts

Customer-facing 2FA:

  1. Install miniOrange 2 Factor Authentication or WP 2FA plugin
  2. Configure to allow (or require) 2FA for customers
  3. WP 2FA supports TOTP (Google Authenticator, Authy), email codes, and backup codes

Social login for WooCommerce: Install Nextend Social Login (free/premium) — supports Google, Facebook, Apple, and Twitter/X sign-in on WooCommerce login and registration pages.

Compromised password detection: Install WPassword or implement a custom check against the HaveIBeenPwned API during registration and password changes.


BigCommerce

Admin two-factor authentication:

  1. Go to Settings → Account Settings → Security
  2. Enable Two-Step Verification; BigCommerce supports authenticator apps and SMS

Customer account security: BigCommerce does not expose customer-facing 2FA natively. Options:

  • Use Stencil (BigCommerce's storefront framework) to add a custom verification step on the customer login page
  • Use an identity provider (Auth0, Okta) for customer authentication — this provides full MFA support and credential monitoring

Google/Social sign-in for BigCommerce: Integrate via BigCommerce's customer login API with a social identity provider. Auth0 provides a turnkey solution with a BigCommerce integration.


Custom / Headless

For custom storefronts, implement security controls at each layer.

Rate limiting on the login endpoint:

import { Ratelimit } from '@upstash/ratelimit';
import { Redis } from '@upstash/redis';

const redis = Redis.fromEnv();
const ipLimiter = new Ratelimit({ redis, limiter: Ratelimit.slidingWindow(20, '15 m'), prefix: 'rl_login_ip' });
const accountLimiter = new Ratelimit({ redis, limiter: Ratelimit.slidingWindow(5, '15 m'), prefix: 'rl_login_email' });

export async function checkLoginRateLimit(ip: string, email: string) {
  const [ipResult, accountResult] = await Promise.all([
    ipLimiter.limit(ip),
    accountLimiter.limit(email.toLowerCase()),
  ]);
  if (!ipResult.success) throw new Error('TOO_MANY_REQUESTS_IP');
  if (!accountResult.success) throw new Error('ACCOUNT_TEMPORARILY_LOCKED');
}

Secure password hashing (Argon2id):

import { hash, verify } from 'argon2';

export const hashPassword = (password: string) =>
  hash(password, { type: 2 /* argon2id */, memoryCost: 65536, timeCost: 3, parallelism: 4 });

export const verifyPassword = (storedHash: string, password: string) =>
  verify(storedHash, password);

TOTP-based MFA:

import { authenticator } from 'otplib';

export function generateMFASecret(): string {
  return authenticator.generateSecret(32);
}

export function verifyTOTP(secret: string, token: string): boolean {
  authenticator.options = { window: 1 }; // Allow ±30-second drift only
  return authenticator.verify({ token, secret });
}

Secure session cookies:

// Set session cookies with httpOnly, Secure, SameSite=Strict
response.cookies.set('session_token', token, {
  httpOnly: true,    // Not accessible to JavaScript — prevents XSS theft
  secure: true,      // HTTPS only
  sameSite: 'strict', // CSRF protection
  maxAge: 30 * 24 * 60 * 60,
  path: '/',
});

Send security alert emails for sensitive account changes: Always notify customers via email when:

  • Password is changed
  • Email address is changed
  • A new device or location logs in
  • MFA is disabled

Best Practices

  • Use passwordless login when possible — Shopify's new customer accounts use one-time codes, eliminating the credential-stuffing attack surface entirely
  • Return the same error for "user not found" and "wrong password" — never reveal which was wrong; this prevents user enumeration
  • Offer MFA, but only require it for admin and high-value accounts — mandatory MFA for all customers increases abandonment; use it for B2B, admin, and customers with saved payment methods
  • Send security alert emails for every sensitive change — password changes, email changes, new device logins, and MFA changes must trigger immediate notification to the customer's confirmed email
  • Review and rotate admin credentials quarterly — a compromised admin account can expose all customer data
  • Use Social login (Google/Apple) as a more secure alternative — these providers handle password security and may prompt for their own MFA

Common Pitfalls

ProblemSolution
WooCommerce login has no rate limitingInstall Wordfence or Limit Login Attempts Reloaded immediately on any live WooCommerce site
Admin account compromised via credential stuffingEnable 2FA for all admin users; use strong, unique passwords for each admin; never reuse admin credentials across services
TOTP codes working indefinitely (custom builds)Use window: 1 in otplib to accept only ±30-second drift; never accept codes older than 90 seconds
Refresh token stored in localStorageStore refresh tokens in httpOnly cookies only; localStorage is accessible to JavaScript and vulnerable to XSS
Rate limit bypass by rotating email variationsNormalize email addresses (lowercase, strip + aliases before the @) before applying per-account rate limiting

Related Skills

  • @secure-checkout
  • @fraud-detection
  • @gdpr-ecommerce
  • @bot-protection

平台分布

Codex

34.25%
按下载量换算48

Claude

30.92%
按下载量换算43

Cursor

18.56%
按下载量换算26

Gemini CLI

8.64%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills