OpenClaw Package Publishing
This directory is the canonical source for the @aws/aws-agents-pay
OpenClaw package. The published artifact also contains the canonical
agents-pay skill staged from the parent skill directory.
Release versions
- Initial release:
1.0.0 - Scoped install compatibility fix:
1.0.1 - Bundled canonical skill and external setup guidance:
1.0.2 - Setup discoverability improvements:
1.0.5 - AgentCore CLI 0.26.x compat and flag clarity:
1.0.6 - Clean-install onboarding and generated-config safety:
1.0.7
Do not publish until the package has passed the checks below and the publisher has given explicit approval.
Reproducible build and tests
cd plugins/aws-agents/skills/agents-pay/packages/openclaw
npm ci
npm test
npm audit --audit-level=moderateThe committed lockfile pins the complete dependency graph. OpenClaw is an optional peer because the package is loaded by an existing OpenClaw host.
Validate and pack
Use the pinned ClawHub CLI release:
npx --yes clawhub@0.23.1 package validate . \
--runtime --allow-execute --json
npx --yes clawhub@0.23.1 package pack . \
--pack-destination ./artifacts --jsonFor inspection against a local OpenClaw checkout, add:
--openclaw /absolute/path/to/sample-OpenClaw-on-AWS-with-BedrockRecord the generated tarball SHA-256 and verify it before publication:
shasum -a 256 artifacts/*.tgz
npx --yes clawhub@0.23.1 package verify artifacts/*.tgz \
--sha256 <recorded-sha256> --jsonSmoke-test installation against the minimum supported OpenClaw version:
OPENCLAW_TEST_HOME=$(mktemp -d)
HOME="$OPENCLAW_TEST_HOME" npx --yes openclaw@2026.3.24 \
plugins install artifacts/*.tgzPublication dry run
Run this before requesting publication approval:
npx --yes clawhub@0.23.1 package publish . \
--family code-plugin \
--name @aws/aws-agents-pay \
--version 1.0.7 \
--tags latest \
--source-repo aws/agent-toolkit-for-aws \
--source-commit <release-commit-sha> \
--source-ref <release-branch-or-tag> \
--source-path plugins/aws-agents/skills/agents-pay/packages/openclaw \
--dry-run --jsonStop after the dry run. Publishing, creating a payment session, and spending testnet funds each require separate explicit approval.
Post-publication validation
Install the release on the supplied OpenClaw deployment and validate x402 v2 only:
- Confirm the package version and the two-tool runtime inventory.
- Confirm paid replay uses
PAYMENT-SIGNATURE. - Refuse unapproved recipient, value, asset, scheme, network, origin, SSRF,
and redirect cases before
ProcessPayment; separately verify explicitallowAnyRecipientmode retains every non-recipient control. - Confirm signed proofs and paid response bodies never appear in tool output or gateway logs.
- Complete one approved Base Sepolia payment.
- Roll back to the prior plugin and configuration.
Apply any validation fix to this canonical directory first and rerun the checks. The consuming package uses the published artifact and does not carry a source snapshot.