npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@axon-chain/axon-skills

v0.2.0

Published

Installable Axon skill bundles that teach AI agents how to handle Axon mainnet wallet and validator workflows.

Readme

@axon-chain/axon-skills

Install official Axon skill bundles for AI agents with npx.

This package is not a node launcher, wallet app, or SDK. It is a distribution package that copies curated Axon skill folders into agent skill roots so tools such as OpenClaw can discover them and load them at the right time.

What Axon Is

Axon is the Axon Chain mainnet project. The official GitHub README describes it as a general-purpose blockchain for AI agents with:

  • an independent L1 network
  • full EVM compatibility
  • agent-native on-chain capabilities
  • validator and Agent participation flows
  • wallet, RPC, SDK, and contract integration surfaces

For this package, the important operating facts are:

  • node-facing Cosmos chain ID: axon_8210-1
  • wallet-facing EVM chain ID: 8210
  • native token: AXON
  • public JSON-RPC: https://mainnet-rpc.axonchain.ai/

This package exists so an agent can answer three questions without first opening the Axon repository:

  • What is Axon?
  • Which Axon workflow is this request asking for?
  • Which official Axon resources should I use next?

After installation, the agent gets:

  • axon-validator-node: an operator playbook for Axon mainnet validator, Agent-validator, and sync-node work
  • axon-mainnet-user: a user-and-Agent playbook for Axon mainnet users, non-validator Agents, balances, transfers, and public RPC reads

Install this package when you want the agent to understand:

  • what Axon task it is handling
  • which skill it should trigger
  • which chain IDs, RPC endpoints, and guardrails apply
  • which reference files it should read next for exact steps

What The Agent Can Do

With these installed skills, an agent can:

  • explain what Axon is at a high level and separate wallet flows from validator flows
  • configure Axon in MetaMask or other EVM wallets with the correct chain ID and RPC
  • inspect chain state through the public JSON-RPC endpoint
  • guide validator and sync-node bootstrap using the official public scripts
  • help check funding, sync state, create-validator, Agent registration, and heartbeat flows
  • point builders to the official SDKs, contract interfaces, release artifacts, and mainnet files

Role Guide

This package is now structured around three user intents:

  • ordinary users who only need wallet access, transfers, balances, and public RPC usage
  • users who want to become an active Agent and understand how Agent rewards work
  • users who want to become a validator and understand validator duties and validator-side rewards

The package still installs two skills, but each skill owns a clear scope:

  • axon-mainnet-user covers ordinary-user flows and non-validator active-Agent flows
  • axon-validator-node covers validator and agent-validator flows

Ordinary Users: How To Use Axon

Ordinary users do not need to run a node or become a validator.

They typically need to:

  • add Axon mainnet to an EVM wallet with chain ID 8210
  • hold AXON for transfers and gas
  • check balances and send transfers
  • inspect public chain state through https://mainnet-rpc.axonchain.ai/
  • connect EVM applications that support Axon mainnet

This path should trigger axon-mainnet-user.

Active Agent: Lifecycle And Reward Logic

Users who want to participate as active Agents without validator duties should stay in axon-mainnet-user, because the user skill now includes dedicated Agent guidance for:

  • how to register an Agent
  • how to keep the Agent online and active
  • what causes reputation to rise or fall
  • how Agent-side rewards are split between reputation rewards and contribution rewards
  • when stake matters for non-validator Agent earnings

At a high level:

  • a registered Agent is not the same thing as a validator
  • a non-validator Agent can still earn Agent-side rewards
  • becoming an active Agent does not require validator duties

Validators: Duties And Reward Logic

Users who want to become validators should also use axon-validator-node.

That skill now separates:

  • the operational path to become a validator
  • validator rights and obligations
  • the extra steps to become an Agent validator
  • validator mining and reward mechanics

At a high level:

  • validators must be funded, synced, and created on chain before operating
  • validators must protect signing keys and avoid downtime and double-signing
  • validator-side rewards depend on proposer selection and validator-pool distribution
  • Agent validators additionally depend on heartbeat freshness, reputation, and stake-weighted mining power

Included skills

  • validator: installs axon-validator-node for validator, Agent-validator, and sync-node operations
  • user: installs axon-mainnet-user for wallet setup, active-Agent flows, balances, transfers, and public RPC usage
  • all: installs both skills

Install

npx @axon-chain/axon-skills install validator
npx @axon-chain/axon-skills install user
npx @axon-chain/axon-skills install all

Default installs copy skills into both agent roots:

  • ${OPENCLAW_STATE_DIR:-~/.openclaw}/skills
  • ${AGENTS_SKILLS_DIR:-${AGENTS_HOME:-~/.agents}/skills}

Repeat installs replace the packaged skill folders in place so updates are easy to roll out.

Commands

npx @axon-chain/axon-skills list
npx @axon-chain/axon-skills install validator
npx @axon-chain/axon-skills install user
npx @axon-chain/axon-skills install all
npx @axon-chain/axon-skills install all --dry-run
npx @axon-chain/axon-skills install validator --dest /path/to/skills

How Agents Use It

The installed folders are normal skill folders with SKILL.md entrypoints and bundled references. An agent reads the skill metadata to decide when to trigger it, then reads the body and reference files to answer Axon-specific requests safely.

In practice:

  • wallet, public RPC, Agent registration, active-Agent, and Agent-reward requests should trigger axon-mainnet-user
  • validator, sync, recovery, validator-economics, and agent-validator requests should trigger axon-validator-node
  • the package gives the agent domain rules and routing, not a running service

Official GitHub References

Use these as the source of truth when more detail is needed:

Verify

openclaw skills list

If OpenClaw is not installed on the current machine, inspect the installed skill folders directly under the target roots and confirm SKILL.md exists in each installed directory.