← Back to Skills Marketplace
agnicpay-prog

Agnic Authenticate Wallet

by Agnic.AI · GitHub ↗ · v2.0.2 · MIT-0
cross-platform ✓ Security Clean
124
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install agnicpay-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 is coherent with its purpose, but before using it: 1) Verify the CLI package identity (npm package 'agnic') and prefer pinned versions over '@latest' when running in production, since npx will execute code fetched at runtime. 2) Use short-lived or least-privilege API tokens and avoid placing long-lived secrets in shared shells. 3) Be aware the CLI will write credentials to ~/.agnic/config.json (0600) — check that file's contents and permissions. 4) The registry metadata omits AGNIC_TOKEN and the config path referenced in SKILL.md; if you need higher assurance, ask the publisher for the package homepage/source and review the CLI code before running it in sensitive environments.
Capability Analysis
Type: OpenClaw Skill Name: agnicpay-authenticate-wallet Version: 2.0.2 The skill provides instructions and tool access for authenticating with the Agnic platform using its official CLI tool via `npx`. It supports both interactive OAuth and headless token-based authentication. The allowed commands are strictly limited to `status` and `auth` operations, and the documentation accurately describes standard credential management practices (e.g., storing tokens in `~/.agnic/config.json`). No indicators of malicious intent or data exfiltration were found.
Capability Tags
cryptorequires-walletrequires-oauth-tokenrequires-sensitive-credentials
Capability Assessment
Purpose & Capability
Name/description (authenticate Agnic wallet via browser OAuth or token) align with the runtime instructions, which call the Agnic CLI (npx agnic@latest) to perform OAuth and token-based auth.
Instruction Scope
SKILL.md only instructs running the Agnic CLI commands (status, auth login, auth logout) and explains expected local behavior (starts a temporary localhost server, opens browser, stores credentials in ~/.agnic/config.json). It does not ask the agent to read unrelated system files or exfiltrate data. Minor mismatch: the metadata declares no config paths or env vars, but the instructions explicitly reference AGNIC_TOKEN and ~/.agnic/config.json.
Install Mechanism
This is an instruction-only skill (no install spec). It instructs using 'npx agnic@latest', which will fetch and execute the package from the npm registry at runtime. That is expected for a CLI, but executing code from @latest is a moderate operational risk—verify the package/source before running in sensitive environments.
Credentials
No required environment variables are declared in the registry metadata, but SKILL.md expects an AGNIC_TOKEN env var (or --token). Requesting an API token for authentication is proportionate to the skill's purpose. The CLI also stores credentials in ~/.agnic/config.json (0600) — this is expected for a CLI but is a material effect on the user's home directory that the metadata did not list.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent platform-level privileges or changes to other skills; storing tokens locally is normal for an auth CLI.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install agnicpay-authenticate-wallet
  3. After installation, invoke the skill by name or use /agnicpay-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: - Added headless authentication (AGNIC_TOKEN env var + --token flag) - AI agents / CI / server environments can now authenticate without a browser - Rebranded references from "AgnicPay" to "Agnic"
v1.0.0
- Initial release of the AgnicPay wallet authentication skill. - Supports sign in, authentication, and wallet connection via browser-based OAuth. - Provides CLI commands for login (`npx agnic@latest auth login`), status checking, and logout. - Credentials are stored securely and tokens auto-refresh for seamless sessions. - Clear error messages and instructions for handling common authentication issues.
Metadata
Slug agnicpay-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?

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 124 downloads so far.

How do I install Agnic Authenticate Wallet?

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

Is Agnic Authenticate Wallet free?

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

Which platforms does Agnic Authenticate Wallet support?

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

Who created Agnic Authenticate Wallet?

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

💬 Comments