← Back to Skills Marketplace
agnicpay-prog

Agnic Authenticate Wallet (x402)

by Agnic.AI · GitHub ↗ · v2.0.2 · MIT-0
cross-platform ✓ Security Clean
234
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install agnic-authenticate-wallet
Description
Authenticate Agnic wallet via browser OAuth or headless API token. Use when the user wants to sign in, log in, authenticate, connect wallet, set up CLI, or r...
README (SKILL.md)

Authenticating the Agnic Wallet

Check Current Status

npx agnic@latest status --json

If already authenticated, no further action needed. If not, choose the appropriate mode below.

Mode 1: Headless / Token Auth (CI, servers, agents)

Preferred when no browser is available. Generate an API token at app.agnic.ai > Settings > API Tokens.

Option A -- Environment variable (recommended for automation):

export AGNIC_TOKEN=\x3Cyour-api-token>
npx agnic@latest status --json

The CLI reads AGNIC_TOKEN automatically. All subsequent commands in the same shell session use it without extra flags.

Option B -- Inline flag (one-off commands):

npx agnic@latest --token \x3Cyour-api-token> status --json

Mode 2: Browser OAuth (interactive terminals)

Use when a browser is available:

npx agnic@latest auth login

This command:

  1. Starts a temporary local server on a random port
  2. Opens the default browser to the Agnic OAuth consent screen
  3. The user signs in (email, Google, or wallet) and approves spending limits
  4. The browser redirects back to http://localhost:\x3Cport>/callback
  5. The CLI exchanges the authorization code for tokens and saves them locally

Wait for the CLI to print Authenticated! before proceeding.

Verify Authentication

npx agnic@latest status --json

Expected output:

{
  "authenticated": true,
  "userId": "did:privy:...",
  "email": "[email protected]",
  "walletAddress": "0x...",
  "tokenExpiry": "2026-05-22T14:30:00Z"
}

Logout

To remove stored credentials:

npx agnic@latest auth logout

Token Storage

  • Browser mode: credentials stored in ~/.agnic/config.json with 0600 permissions. Tokens auto-refresh on 401 responses. Refresh token expires after 90 days.
  • Token mode: no local storage. The token is read from AGNIC_TOKEN env var or --token flag per invocation.

Error Handling

  • "Not authenticated" -- Set AGNIC_TOKEN env var, pass --token, or run auth login
  • "Authentication failed" -- User cancelled the browser flow or the 5-min timeout expired
  • "Could not open browser" -- The CLI prints a URL to copy and open manually
  • "Token expired" -- Browser tokens auto-refresh; API tokens must be regenerated at app.agnic.ai
  • "Invalid token" -- Check the token value; it may have been revoked or malformed
Usage Guidance
This skill appears to do what it says: it instructs the agent to run the Agnic CLI via 'npx' to perform OAuth or token-based authentication and to store tokens under ~/.agnic/config.json. Before using it: (1) ensure you have Node/npm and are comfortable with running 'npx' (it downloads and executes code from the npm registry); consider pinning to a specific version instead of @latest; (2) prefer setting AGNIC_TOKEN for non-interactive environments and avoid storing long-lived tokens on shared machines; (3) after browser auth, verify ~/.agnic/config.json permissions and contents; (4) if you need stronger assurance, review the agnic npm package/source (or install from an official release) before running commands that fetch code.
Capability Analysis
Type: OpenClaw Skill Name: agnic-authenticate-wallet Version: 2.0.2 The skill bundle provides standard instructions and tool definitions for authenticating with the Agnic CLI via OAuth or API tokens. It uses legitimate patterns such as 'npx agnic@latest' for status checks and authentication flows, and it correctly identifies sensitive file locations like ~/.agnic/config.json for credential storage. No evidence of data exfiltration, malicious execution, or prompt injection was found in SKILL.md or _meta.json.
Capability Tags
cryptorequires-walletrequires-oauth-tokenrequires-sensitive-credentials
Capability Assessment
Purpose & Capability
The skill's name/description match the instructions: it tells users how to authenticate via browser OAuth or an API token. However the manifest lists no required binaries while the instructions require 'npx' (Node/npm) to run the CLI; that's a small mismatch but explainable.
Instruction Scope
SKILL.md restricts actions to running 'npx agnic' commands, reading an optional AGNIC_TOKEN env var, and storing credentials in ~/.agnic/config.json. Those behaviors are within scope for an auth helper, but the manifest did not declare the config path (~/.agnic/config.json) that the CLI writes, which is a disclosure gap.
Install Mechanism
No install spec (instruction-only), but the runtime uses 'npx agnic@latest' which fetches and executes the package from npm on demand. That's expected for a CLI helper but carries the usual supply-chain risk of running remotely fetched code, especially when using the @latest tag.
Credentials
The only credential surface is the optional AGNIC_TOKEN env var and tokens stored locally by the CLI. No unrelated secrets or multiple unrelated credentials are requested. The manifest did not list AGNIC_TOKEN in requires.env even though SKILL.md documents it, which is a minor proportionality/documentation mismatch.
Persistence & Privilege
The skill does not request elevated/platform-wide persistence. It documents storing auth tokens in its own config file (~/.agnic/config.json) with 0600 — expected for an auth flow. always:false and normal invocation flags are appropriate.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install agnic-authenticate-wallet
  3. After installation, invoke the skill by name or use /agnic-authenticate-wallet
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.2
v2.0.2 — Synced with upstream agnic-wallet-skills authenticate-wallet skill: - Added headless authentication (AGNIC_TOKEN env var + --token flag) - Rebranded references from "AgnicPay" to "Agnic"
v1.0.0
- Initial release of authenticate-wallet skill. - Provides authentication for AgnicPay wallets via browser OAuth or token-based headless mode. - New CLI commands support login, token status checking, and logout. - Step-by-step documentation for both interactive and headless authentication flows. - Includes guidance on error handling and credential removal.
Metadata
Slug agnic-authenticate-wallet
Version 2.0.2
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Agnic Authenticate Wallet (x402)?

Authenticate Agnic wallet via browser OAuth or headless API token. Use when the user wants to sign in, log in, authenticate, connect wallet, set up CLI, or r... It is an AI Agent Skill for Claude Code / OpenClaw, with 234 downloads so far.

How do I install Agnic Authenticate Wallet (x402)?

Run "/install agnic-authenticate-wallet" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Agnic Authenticate Wallet (x402) free?

Yes, Agnic Authenticate Wallet (x402) is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Agnic Authenticate Wallet (x402) support?

Agnic Authenticate Wallet (x402) is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Agnic Authenticate Wallet (x402)?

It is built and maintained by Agnic.AI (@agnicpay-prog); the current version is v2.0.2.

💬 Comments