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.
git clone --depth 1 https://github.com/epistemedeus/x402-url-extractornpx agentmods add skills/epistemedeus/x402-url-extractor/explicit-recordWrote 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.
[](https://agentmods.dev/skills/epistemedeus/x402-url-extractor/explicit-record)<a href="https://agentmods.dev/skills/epistemedeus/x402-url-extractor/explicit-record"><img src="https://agentmods.dev/badge/skills/epistemedeus/x402-url-extractor/explicit-record/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.
<a href="https://agentmods.dev/skills/epistemedeus/x402-url-extractor/explicit-record"><img src="https://agentmods.dev/badge/skills/epistemedeus/x402-url-extractor/explicit-record.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00077 | $0.01126 |
| Opus 5.5 | $0.00031 | $0.00450 |
| Sonnet 5.5 | $0.00015 | $0.00225 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
explicit-record 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map held extract JSON into buyer records
This skill runs the public offline record CLI. It does not fetch URLs, pay,
sign, guess entities, choose a Product or sameAs value, or add a second
price. Paid observation acquisition stays on web-extract and the public
customer example.
Exact inputs
Required, already on disk:
--input: deliveredGET /extractorPOST /extract/batchJSON--mapping: buyer JSON with one JSON Pointer per named field--schema: buyer local JSON Schema for those field names--out: a fresh or empty directory
Do not invent pointers, field names, entities, or schema properties. If input,
mapping, or schema is missing, ask for it. If no output location is specified,
choose a fresh temporary directory and report its path. Mapping targets are flat field
names. kind is extract, extract_batch, or json. Each field from is
an explicit JSON Pointer with base document, row, or item.
Use the full public repository checkout, not a separately packed npm tarball.
From examples/customer-x402 after npm ci:
npm run record -- \
--input ./fixtures/record/product-jsonld/delivery/extract-batch.json \
--mapping ./fixtures/record/product-jsonld/mapping.json \
--schema ./fixtures/record/product-jsonld/schema.json \
--out /tmp/samedaydesk-record-product
npm run record -- \
--input ./fixtures/record/org-contact/delivery/extract.json \
--mapping ./fixtures/record/org-contact/mapping.json \
--schema ./fixtures/record/org-contact/schema.json \
--out /tmp/samedaydesk-record-org
In those two buyer mappings, missing product sku and organization email
are optional. For an executable required-field example, reuse the product
delivery with a separate buyer mapping and schema that require sku:
npm run record -- \
--input ./fixtures/record/product-jsonld/delivery/extract-batch.json \
--mapping ./fixtures/record/required-sku/mapping.json \
--schema ./fixtures/record/required-sku/schema.json \
--out /tmp/samedaydesk-record-required-sku
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.
- 1mo ago First seen · 108 lines · 77 tokens per session scan A 509c816d00d4
explicit-record is a skill published in the GitHub repository epistemedeus/x402-url-extractor (1 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,126 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-09-09.
Other skills, from other repositories
x402
Monetize any user project/service with the x402 payment protocol on platform networks (Base + Monad + Robinhood + X Layer + Solana; Starchild platform billing: payperuse / lifetime / weekly / monthly / quarterly / yearly / prepaid, plus multi-plan services), limited-time free promotions (amount-0 verify, no…
bankr-shopify
Shopify Admin & Storefront GraphQL APIs via curl, with Bankr-native bridges. Manage products, orders, customers, inventory, metafields, webhooks, and bulk ops, then wire merchant data to onchain primitives — store a Bankr-resolvable handle (ENS, Twitter, Farcaster, wallet) on each customer as a metafield, expose…
scvd-general-store
A live x402 practice counter: real settlement, no sandbox, from $0.001. Free conformance checking for any issuer's signed offers and receipts, ours or a competitor's. An evidence observatory: signed observation of what other endpoints and payments actually did, never a ranking. Reachable six ways, including browser…
scvd-x402-verification
Check an x402 endpoint before paying it, and check the receipt after. Free instruments first; a paid signed observation only when durable third-party evidence is actually needed.
scvd-x402-verification
Check an x402 endpoint before paying it, and check the receipt after. Free instruments first; a paid signed observation only when durable third-party evidence is actually needed.
x402-before-you-pay
Before an agent pays an x402 endpoint, read its 402 terms and run scvd.store's free preflight and dry run over the same bytes; decide pay / donotpay / cannottell with every reason named. Use when code or an agent is about to call a paid x402 URL, when a 402 looks wrong, or when a payment "never went through".…