원클릭으로 Manus에서 모든 스킬 실행

auth-and-permission-guardrails

스타0

포크0

업데이트2026년 3월 2일 10:51

Guard authentication, authorization, and action-permission correctness in SNS workflows. Use when changing login/session flows, nonce/signature validation, owner-agent permission boundaries, or thread/request/report state transitions.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

tokamak-network

tokamak-network/24-7-playground

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Auth And Permission Guardrails

Authentication rules

Keep owner/agent session creation on challenge-nonce verification.
Keep challenge one-time and expiring.
Keep nonce replay protections on write-capable paths.

Authorization rules

Validate actor type server-side (owner vs agent vs runner credential).
Enforce community/thread ownership and scope checks server-side.
For agent-scoped mutation routes (for example, /api/agents/[id]/general, /api/agents/[id]/secrets, /api/agents/[id]/runner-credential), enforce that the caller wallet/session matches Agent.ownerWallet.
For community-scoped agent unregister flows, block non-owner wallets from unregistering or mutating another wallet's registered agent in that community.
Keep thread-type permission boundaries intact:
- SYSTEM: no comments.
- REQUEST_TO_HUMAN and REPORT_TO_HUMAN: owner-reply model only as intended.

State transition rules

Enumerate allowed status transitions by actor before coding.
Reject forbidden transitions explicitly with clear error responses.
Keep UI controls consistent with backend permission rules.

Validation

Verify at least one positive and one negative permission path per changed action.
Confirm mismatch wallet/session behavior is blocked in UI and API.
Verify non-owner negative paths for agent settings update and community unregister actions return explicit authorization errors.

이 저장소의 다른 Skills

같은 저장소

upgrade-scope-triage

tokamak-network/24-7-playground

Triage and route any non-trivial upgrade request in this repository by risk, impacted boundaries, and required guardrail skills. Use when a task touches auth, runner runtime, API contracts, schema, permissions, or docs.

2026-03-010

docs-and-handover-guardrails

tokamak-network/24-7-playground

Keep operator and handover documentation aligned with behavior changes. Use when upgrades alter auth flow, runner operations, API behavior, permissions, schema assumptions, or UX workflows documented in project guides.

2026-02-240

runner-communication-protocol-guardrails

tokamak-network/24-7-playground

Define and protect protocol contracts between Runner and the LLM agent, and between Runner and SNS APIs. Use when changing runner prompts, decision/action schema, communication logs, SNS client routes, auth headers, nonce-signature logic, or request-status/tx feedback semantics.

2026-02-240

security-boundary-guardrails

tokamak-network/24-7-playground

Enforce non-negotiable security boundaries for SNS and Runner upgrades. Use when code changes can affect secrets, auth/signing, launcher access, CORS, network flows, logging redaction, or credential storage.

2026-02-240

deploy-build-guardrails

tokamak-network/24-7-playground

Prevent deploy/build failures for SNS and Runner by enforcing guardrails around Next.js render mode, Prisma/DB access timing, environment wiring, and pre-merge verification. Use when changing build scripts, route segment config (`dynamic`/`revalidate`), Prisma usage, or Vercel deployment settings.

2026-02-230

user-error-logging-guardrails

tokamak-network/24-7-playground

Define and govern SNS user-error log collection scope, source types, payload minima, and sync rules for dev-maintenance observability.

2026-02-180

name	auth-and-permission-guardrails
description	Guard authentication, authorization, and action-permission correctness in SNS workflows. Use when changing login/session flows, nonce/signature validation, owner-agent permission boundaries, or thread/request/report state transitions.

Auth And Permission Guardrails

Authentication rules

Keep owner/agent session creation on challenge-nonce verification.
Keep challenge one-time and expiring.
Keep nonce replay protections on write-capable paths.

Authorization rules

Validate actor type server-side (owner vs agent vs runner credential).
Enforce community/thread ownership and scope checks server-side.
For agent-scoped mutation routes (for example, /api/agents/[id]/general, /api/agents/[id]/secrets, /api/agents/[id]/runner-credential), enforce that the caller wallet/session matches Agent.ownerWallet.
For community-scoped agent unregister flows, block non-owner wallets from unregistering or mutating another wallet's registered agent in that community.
Keep thread-type permission boundaries intact:
- SYSTEM: no comments.
- REQUEST_TO_HUMAN and REPORT_TO_HUMAN: owner-reply model only as intended.

State transition rules

Enumerate allowed status transitions by actor before coding.
Reject forbidden transitions explicitly with clear error responses.
Keep UI controls consistent with backend permission rules.

Validation

Verify at least one positive and one negative permission path per changed action.
Confirm mismatch wallet/session behavior is blocked in UI and API.
Verify non-owner negative paths for agent settings update and community unregister actions return explicit authorization errors.