Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add zpoint/vibe-seller --skill amazon-fba-inboundgit clone --depth 1 https://github.com/zpoint/vibe-sellerWrote 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/zpoint/vibe-seller/amazon-fba-inbound)<a href="https://agentmods.dev/skills/zpoint/vibe-seller/amazon-fba-inbound"><img src="https://agentmods.dev/badge/skills/zpoint/vibe-seller/amazon-fba-inbound/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/zpoint/vibe-seller/amazon-fba-inbound"><img src="https://agentmods.dev/badge/skills/zpoint/vibe-seller/amazon-fba-inbound.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 3 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00085 | $0.07225 |
| Opus 5 | $0.00043 | $0.03612 |
| Sonnet 5 | $0.00017 | $0.01445 |
| Haiku 4.5 | $0.00009 | $0.00722 |
Grade A, and why
amazon-fba-inbound 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 12d 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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amazon FBA inbound — Send to Amazon, end to end
Creating an inbound shipment, quoting it, confirming it, printing box labels, and voiding one. Covers both the ordinary path (your own carrier or an Amazon-partnered domestic carrier) and the cross-border SEND programme, which is browser-only.
Load amazon-shared first — it owns marketplace TLDs, the sign-in
challenge loop, and the Ziniao/OTP/passkey rules. This skill assumes you
are already signed in.
0. Why a browser at all
For most inbound work an API exists. For SEND it does not, and that is worth knowing before you look for one:
GET /inbound/fba/2024-03-20/inboundPlans/{id}on a SEND plan answers400 BadRequest: GetInboundPlan is not supported for the cross border Seller Export and Delivery programlistInboundPlansomits SEND plans entirely- a plan you create through the API is an ordinary FBA plan, so
listTransportationOptionsonly ever offersUSE_YOUR_OWN_CARRIER— no partnered option appears - the old v0 partnered flow (
/shipments/{id}/transport) answers400 This API is deprecated
The trap: the SEND partners are in the option list
The carriers Amazon names as its SEND partners do come back from
listTransportationOptions, by carrier.alphaCode. Picking one does
not book a SEND shipment — it books that company as a carrier you
arranged. Same haulier, different product, and the difference is
everything: no Amazon-arranged freight, no Amazon-issued tracking, no
partnered price, and the shipment then waits on you for pallet or
tracking details.
Verified end to end on a live account: confirming a SEND partner's
USE_YOUR_OWN_CARRIER option produced a shipment with
freightInformation: null and no quote — Amazon arranged and priced
nothing.
The shipment's name tells you nothing about which one you have. That
API-confirmed non-SEND shipment was auto-named FBA STA (…), and a
genuine SEND shipment booked through the portal on the same account
hours later was also named FBA STA (…) — while older genuine SEND
shipments there read FBA SEA (…). STA is just "Send To Amazon", and
the SEA/STA difference is naming history, not product. Reading the
name as evidence is how a real SEND booking gets mistaken for the trap.
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.
- 12d ago First seen · 571 lines · 85 tokens per session scan A 2e654e85d99b
amazon-fba-inbound is a skill published in the GitHub repository zpoint/vibe-seller (67 stars, last pushed yesterday), licensed Apache-2.0. It adds 85 tokens to every session and 7,225 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
ebay-search-listing
Extracts product listings from any eBay search or category page URL, returning per-item cards (itemNumber, url, title, subtitle, caption, price, priceWithCurrency, currency, wasPrice, bids, shipping, seller, sellerFeedbackCount, sellerPositiveRating, reviewsCount, starRating, image) plus pagination state (currentPage…
amazon-bestseller-listing
Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…
amazon-search-listing
Amazon search and category listing scraper: extract product listings from any Amazon search results page, keyword search URL, or category browse page and return per-item cards (asin, title, url, image, price, listPrice, stars, reviewCount, badges, isAmazonChoice, isBestSeller, isSponsored, delivery, boughtInPast…
etsy-category-listing
Etsy category page scraper: given an Etsy category URL (e.g. https://www.etsy.com/c/jewelry) and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from category and subcategory…
etsy-product-detail
Etsy product detail scraper: given an Etsy listing URL, returns full product detail including listingId, title, priceCurrent, priceOriginal, currency, images (all), description, shopName, shopUrl, rating, reviewCount, favorites, inCartCount, variations (with per-option price ranges), highlights, listedDate…
etsy-shop-catalog
Etsy shop catalog scraper: given an Etsy shop URL (e.g. https://www.etsy.com/shop/{shop-name}) and optional page number, returns paginated product listings from that shop's own storefront with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping…