Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器github未标认证来源可访问许可证需确认审计提醒

nodeops-auth节点操作验证

Agent Skill

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

总安装

10,127

周安装

435

GitHub Stars

3

下载量

3,550
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/nodeops-app/skills --skill nodeops-auth

简介

nodeops-auth 用于辅助安全审计、权限检查和认证流程分析。

  • 适合梳理敏感配置、检查依赖风险或生成安全复核清单。
  • 支持常见漏洞排查和鉴权逻辑审查,提升系统安全性。
  • 安装命令:npx skills add https://github.com/nodeops-app/skills --skill nodeops-auth。
  • 不能将工具输出直接作为结论,涉及密钥或生产系统时需确认最小权限和操作边界。

SKILL.md

NodeOps Auth Setup

Add NodeOps PKCE OAuth to an existing Next.js (App Router) project.

Prerequisites

Before starting, verify the project is compatible:

  • App Router required: Check if app/ directory exists. If only pages/ exists, stop and tell the user: "This skill only supports Next.js App Router. Your project uses Pages Router."
  • Next.js required: Check package.json for next in dependencies. If missing, stop and tell the user this is a Next.js-only package.

Idempotency

Before each step, check if the work is already done. Skip steps that are already complete:

  • If @nodeops-createos/integration-oauth is already in package.json dependencies, skip install.
  • If app/api/auth/me/route.ts and app/api/auth/token/route.ts already exist, skip route creation.
  • If AuthProvider from @nodeops-createos/integration-oauth is already imported in the layout, skip wrapping.
  • If app/callback/page.tsx (or .jsx) already exists, skip callback page creation.
  • If .env.example already exists and contains NODEOPS_, skip env file creation.

Steps

  1. Detect project setup — read package.json and check for lock files:

- Package manager: if pnpm-lock.yaml exists → pnpm, if yarn.lock exists → yarn, else → npm - TypeScript: if tsconfig.json exists use .ts/.tsx extensions, else .js/.jsx - Confirm app/ directory exists (App Router). If only pages/ exists, stop. - Confirm next is in dependencies. If not, stop.

  1. Install the package — run the appropriate install command:

- npm: npm install @nodeops-createos/integration-oauth - pnpm: pnpm add @nodeops-createos/integration-oauth - yarn: yarn add @nodeops-createos/integration-oauth - If install fails: check if the user has network access and the registry is reachable. Suggest running the command manually if it keeps failing.

  1. Create the API routes — create two separate route files, creating directories as needed: app/api/auth/me/route.ts (or .js): export {GET} from '@nodeops-createos/integration-oauth/server/me'; app/api/auth/token/route.ts (or .js): export {POST} from '@nodeops-createos/integration-oauth/server/token';
  2. Wrap layout with AuthProvider — read the root layout file. It could be app/layout.tsx, app/layout.jsx, app/layout.js, or app/layout.ts. Find whichever exists.

- Add the import at the top of the file: import {AuthProvider} from '@nodeops-createos/integration-oauth'; - Find {children} inside the <body> tag. Wrap it with <AuthProvider>: <AuthProvider>{children}</AuthProvider> - Do NOT add "use client" to the layout. AuthProvider is already marked "use client" internally — it works fine when imported from a Server Component layout. - If the layout already has other providers (e.g., ThemeProvider, QueryClientProvider), nest <AuthProvider> alongside them. Do NOT remove or replace existing providers. - If {children} is not directly inside <body> (e.g., it's inside a wrapper div or fragment), wrap wherever {children} appears. - If no layout file exists, stop and tell the user to create a root layout first.

  1. Create the callback page — ask the user: "Where should users be redirected after login? (default: /dashboard)". Use their answer as the redirectTo value. Then create app/callback/page.tsx (or .jsx): "use client"; import {useCallbackHandler} from "@nodeops-createos/integration-oauth"; export default function Callback() {const {loading, error} = useCallbackHandler({redirectTo: "/dashboard"}); if (loading) return (<div style={{display: "flex", justifyContent: "center", alignItems: "center", height: "100vh"}}> <p>Signing in...</p> </div>); if (error) return <p>Login failed: {error}</p>; return null;}
  2. Create .env.example — create this file at the project root: # ── Client-side (exposed to browser via NEXT_PUBLIC_ prefix) ────────────────── NEXT_PUBLIC_NODEOPS_AUTH_URL=https://id.nodeops.network/oauth2/auth NEXT_PUBLIC_NODEOPS_CLIENT_ID=your_client_id_here NEXT_PUBLIC_NODEOPS_REDIRECT_URI=http://localhost:3000/callback NEXT_PUBLIC_NODEOPS_SCOPES=offline_access offline openid # ── Server-side only (never sent to browser) ────────────────────────────────── NODEOPS_CLIENT_SECRET=your_client_secret_here NODEOPS_TOKEN_URL=https://id.nodeops.network/oauth2/token NODEOPS_USERINFO_URL=https://autogen-v2-api.nodeops.network/v1/users/me
  3. Create .env.local — if .env.local does not already exist, copy .env.example to .env.local and remind the user to fill in NEXT_PUBLIC_NODEOPS_CLIENT_ID and NODEOPS_CLIENT_SECRET with their credentials from the NodeOps developer portal. If .env.local already exists, append the missing NODEOPS_ vars only — do NOT overwrite existing values.
  4. Check .gitignore — read .gitignore (if it exists). If .env.local is NOT listed, add it to prevent leaking secrets. Also ensure .env is listed. If no .gitignore exists, create one with at least: .env.env.local
  5. Docker/container deployment — check if a Dockerfile exists in the project root. If it does, verify it handles NodeOps env vars correctly and warn the user if not. If the user asks about Docker or deployment, create or update the Dockerfile. Critical: NEXT_PUBLIC_* vars are baked into the JS bundle at build time by Next.js. They must be set as ENV or ARG in the Dockerfile before RUN npm run build. Setting them only at runtime does nothing — the bundle will contain undefined. The two categories of vars: Variable When needed Why NEXT_PUBLIC_NODEOPS_AUTH_URL Build time Inlined into client JS bundle NEXT_PUBLIC_NODEOPS_CLIENT_ID Build time Inlined into client JS bundle NEXT_PUBLIC_NODEOPS_REDIRECT_URI Build time Inlined into client JS bundle NEXT_PUBLIC_NODEOPS_SCOPES Build time Inlined into client JS bundle NODEOPS_CLIENT_SECRET Runtime only Read by API route on each request NODEOPS_TOKEN_URL Runtime only Read by API route on each request NODEOPS_USERINFO_URL Runtime only Read by API route on each request CreateOS note: CreateOS uses the Dockerfile when one is present. Use a single-stage Dockerfile only — multi-stage builds with COPY --from=builder fail on this platform. Remove the Dockerfile entirely to fall back to CreateOS's default install/run commands. See the CreateOS section (step 10) for the runtime config workaround for NEXT_PUBLIC_* vars. Example Dockerfile (single-stage, compatible with CreateOS): FROM node:20-alpine WORKDIR /app COPY package*.json./ RUN npm ci COPY.. # NEXT_PUBLIC_* must be present at build time — they get baked into the JS bundle ARG NEXT_PUBLIC_NODEOPS_AUTH_URL=https://id.nodeops.network/oauth2/auth ARG NEXT_PUBLIC_NODEOPS_CLIENT_ID ARG NEXT_PUBLIC_NODEOPS_REDIRECT_URI ARG NEXT_PUBLIC_NODEOPS_SCOPES=offline_access offline openid ENV NEXT_PUBLIC_NODEOPS_AUTH_URL=$NEXT_PUBLIC_NODEOPS_AUTH_URL ENV NEXT_PUBLIC_NODEOPS_CLIENT_ID=$NEXT_PUBLIC_NODEOPS_CLIENT_ID ENV NEXT_PUBLIC_NODEOPS_REDIRECT_URI=$NEXT_PUBLIC_NODEOPS_REDIRECT_URI ENV NEXT_PUBLIC_NODEOPS_SCOPES=$NEXT_PUBLIC_NODEOPS_SCOPES # Server-side vars — only needed at runtime, read per-request by API routes ENV NODEOPS_CLIENT_SECRET="" ENV NODEOPS_TOKEN_URL=https://id.nodeops.network/oauth2/token ENV NODEOPS_USERINFO_URL=https://autogen-v2-api.nodeops.network/v1/users/me RUN npm run build EXPOSE 3000 CMD ["npm", "start"] Also ensure .dockerignore excludes .env.local: .env.env.local node_modules.next If the project deploys to Vercel or similar: no Dockerfile is needed — those platforms inject env vars before building automatically. Just remind the user to add the vars in their platform's dashboard.
  6. CreateOS / build-then-inject platforms — CreateOS uses the Dockerfile when one is present, but injects env vars after the build step. This means NEXT_PUBLIC_* vars are undefined at build time even with ARG/ENV in the Dockerfile. Use the runtime config workaround below, or remove the Dockerfile entirely to fall back to CreateOS's default install/run commands. What the package handles automatically (v1.x+) AuthProvider from @nodeops-createos/integration-oauth v1.x+ auto-fetches /api/config at runtime if NEXT_PUBLIC_* vars are missing from the bundle. No extra setup is needed — just make sure the API route exists (step 10a below). If using an older package version, add manually: 10a. Create app/api/config/route.ts (or .js): import {NextResponse} from 'next/server'; export const dynamic = 'force-dynamic'; export async function GET() {return NextResponse.json({NEXT_PUBLIC_NODEOPS_AUTH_URL: process.env.NEXT_PUBLIC_NODEOPS_AUTH_URL || 'https://id.nodeops.network/oauth2/auth', NEXT_PUBLIC_NODEOPS_CLIENT_ID: process.env.NEXT_PUBLIC_NODEOPS_CLIENT_ID || '', NEXT_PUBLIC_NODEOPS_REDIRECT_URI: process.env.NEXT_PUBLIC_NODEOPS_REDIRECT_URI || '', NEXT_PUBLIC_NODEOPS_SCOPES: process.env.NEXT_PUBLIC_NODEOPS_SCOPES || 'offline_access offline openid',});} This route reads NEXT_PUBLIC_* vars from the server environment at runtime (where they ARE available) and exposes them to the client via a JSON endpoint. 10b. Create components/EnvBootstrap.tsx (or .jsx): "use client"; import {useEffect, useState} from "react"; export default function EnvBootstrap({children}: {children: React.ReactNode}) {const [ready, setReady] = useState(// If vars are already baked in (e.g. local dev), skip the fetch typeof window!== "undefined" &&!!process.env.NEXT_PUBLIC_NODEOPS_CLIENT_ID); useEffect(() => {if (ready) return; fetch("/api/config").then((r) => r.json()).then((env) => {// Patch process.env so AuthProvider picks them up Object.assign(process.env, env); setReady(true);}).catch((err) => {console.error("Failed to load runtime config:", err); setReady(true); // render anyway so error states show});}, [ready]); if (!ready) return null; return <>{children}</>;} 10c. Update the root layout to wrap AuthProvider with EnvBootstrap: import {AuthProvider} from '@nodeops-createos/integration-oauth'; import EnvBootstrap from '@/components/EnvBootstrap'; // inside <body>: <EnvBootstrap> <AuthProvider>{children}</AuthProvider> </EnvBootstrap> This ensures env vars are fetched from the server and patched into process.env before AuthProvider initializes on the client.
  7. Show a summary — print a clear summary:

- Files created/modified (list each one) - Files skipped (if any were already present) - Remind user to fill in the 2 required env vars: NEXT_PUBLIC_NODEOPS_CLIENT_ID and NODEOPS_CLIENT_SECRET - If a Dockerfile exists, remind that NEXT_PUBLIC_* vars must be set before npm run build in the Dockerfile - Show how to use the hooks in any page: import {useAuth, useUser} from '@nodeops-createos/integration-oauth'; const {isAuthenticated, login, logout, loading, authError} = useAuth(); const {user} = useUser();

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.67%
按下载量换算1,373

Claude

29.47%
按下载量换算1,046

Cursor

19.15%
按下载量换算680

Gemini CLI

9.35%
按下载量换算332

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills