deltasignal-x402-status

deltasignal-x402-status is a skill for Codex from aitrailblazer/deltasignal-atlas-codex-plugin. It costs 74 tokens per session (585 once invoked), scanned A, original, MIT.

A command-line status tool for checking an x402 seller setup in a specific repository. x402 is a payment protocol, and the tool reports configured wallet details, saved payment records, settlement data, and merchant discovery status.

In plain words
What is it for?
Use it to inspect the seller wallet, payment count, settlement ledger, transaction hashes, saved publication artifacts, and discovery results in JSON or human-readable form.
Why use it?
It brings wallet configuration and locally saved payment evidence into one status check instead of requiring separate inspection of environment settings and artifact files.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./scripts/deltasignal-x402-status.sh.

Good fit Use it to inspect the seller wallet, payment count, settlement ledger, transaction hashes, saved publication artifacts, and discovery results in JSON or human-readable form.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/aitrailblazer/deltasignal-atlas-codex-plugin
agentmods
npx agentmods add skills/aitrailblazer/deltasignal-atlas-codex-plugin/deltasignal-x402-status

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for deltasignal-x402-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/aitrailblazer/deltasignal-atlas-codex-plugin/deltasignal-x402-status/github.svg)](https://agentmods.dev/skills/aitrailblazer/deltasignal-atlas-codex-plugin/deltasignal-x402-status)
Your own site
<a href="https://agentmods.dev/skills/aitrailblazer/deltasignal-atlas-codex-plugin/deltasignal-x402-status"><img src="https://agentmods.dev/badge/skills/aitrailblazer/deltasignal-atlas-codex-plugin/deltasignal-x402-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for deltasignal-x402-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/aitrailblazer/deltasignal-atlas-codex-plugin/deltasignal-x402-status"><img src="https://agentmods.dev/badge/skills/aitrailblazer/deltasignal-atlas-codex-plugin/deltasignal-x402-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 585 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.00585
Opus 5.5 $0.00030 $0.00234
Sonnet 5.5 $0.00015 $0.00117
Haiku 4.5 $0.00007 $0.00059

Measured 6d ago against content hash 351aedca43b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deltasignal-x402-status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

x402/skills/deltasignal-x402-status/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DeltaSignal x402 Status

Use the repo-local status command to inspect the current x402 seller configuration and local payment evidence.

Command

From the aitrailblazer-web-intel-mcp repo root, run:

./scripts/deltasignal-x402-status.sh

Machine-readable output:

./scripts/deltasignal-x402-status.sh --json

Compact payment ledger:

./scripts/deltasignal-x402-status.sh --ledger

What it checks

  • DELTASIGNAL_WALLET_ADDRESS via env or Key Vault-backed secret resolution
  • presence of CDP_API_KEY and CDP_API_SECRET
  • saved publication artifacts under artifacts/x402-bazaar/
  • latest recorded settlement payer, route, and transaction hash
  • compact ledger rows from saved settlements with time, route, price, payer, tx hash, and artifact file
  • CDP merchant discovery for the configured seller wallet when the wallet is present

Workflow

  1. Confirm the working directory is the aitrailblazer-web-intel-mcp repo root.
  2. Run ./scripts/deltasignal-x402-status.sh.
  3. Report the configured seller wallet first.
  4. Report the number of recorded payments from local artifacts.
  5. If merchant discovery succeeds, report the resource count and the merchant query URL.
  6. If the user wants a tabular payment history, run ./scripts/deltasignal-x402-status.sh --ledger.
  7. If the user wants exact settlement details, inspect the newest file in artifacts/x402-bazaar/.

Interpretation

  • seller wallet is the onchain payTo address advertised by DeltaSignal x402 challenges.
  • recorded payments comes from saved publication artifacts, not from Coinbase account statements.
  • merchant resources indicates how many DeltaSignal resources CDP discovery currently associates with the seller wallet.
  • latest tx can be checked on Base explorer or compared against Coinbase transaction history.
  • --ledger is sourced from saved publication artifacts, so it is a local evidence ledger rather than a Coinbase statement export.

Do not do

Read the full file on GitHub · 62 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 62 lines · 74 tokens per session scan A 351aedca43b2

Subscribe to this mod's changes

deltasignal-x402-status is a skill published in the GitHub repository aitrailblazer/deltasignal-atlas-codex-plugin (1 stars, last pushed 7d ago), licensed MIT. It adds 74 tokens to every session and 585 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.