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 lunw/shopline-ai-toolkit-dsh --skill shopline-onboarding-devgit clone --depth 1 https://github.com/lunw/shopline-ai-toolkit-dshWrote 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/lunw/shopline-ai-toolkit-dsh/shopline-onboarding-dev)<a href="https://agentmods.dev/skills/lunw/shopline-ai-toolkit-dsh/shopline-onboarding-dev"><img src="https://agentmods.dev/badge/skills/lunw/shopline-ai-toolkit-dsh/shopline-onboarding-dev/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/lunw/shopline-ai-toolkit-dsh/shopline-onboarding-dev"><img src="https://agentmods.dev/badge/skills/lunw/shopline-ai-toolkit-dsh/shopline-onboarding-dev.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.00056 | $0.00942 |
| Opus 5.5 | $0.00022 | $0.00377 |
| Sonnet 5.5 | $0.00011 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
shopline-onboarding-dev 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SHOPLINE Developer Onboarding
SHOPLINE (商线科技) is an e-commerce SaaS platform popular in Southeast Asia, Taiwan, Hong Kong and Greater China. Apps are built against the OpenAPI and distributed through the Partner Portal (https://developer.myshopline.com/).
When you need store data, pick the API surface first
| Need | Surface | Endpoint shape (store domain: https://{handle}.myshopline.com) |
|---|---|---|
| Store management CRUD (products, orders, customers, inventory) | Admin REST API | POST/GET/DELETE /admin/openapi/{version}/{endpoint}.json |
| Complex store queries, batched writes | Admin GraphQL API | POST /admin/graph/{version}/graphql.json |
| Storefront data (customer-facing catalog, cart) | Storefront API | POST /storefront/graph/{version}/graphql.json |
| Real-time store events | Webhooks | HTTPS callback POSTs (see shopline-webhook) |
| Browser-only / in-theme data | Ajax API | unversioned |
| App/theme UI scripting | Handlebars / Sline | theme templates |
All versioned APIs use quarterly versions vYYYYMMDD (e.g. v20260601). SHOPLINE maintains 8 concurrent versions in a rolling window; stable versions are supported for ~12 months. Always pin the version you develop against and migrate before deprecation.
App types (choose before anything else)
- Public app — sold via the SHOPLINE App Store; must pass app review. OAuth 2.0 authorization.
- Custom app — built in the Developer Center (Partner Portal) for one merchant's stores; no review needed. OAuth 2.0 authorization.
- Private app — created by the merchant in the SHOPLINE Admin (
Apps > Develop Apps > API certificate); no OAuth, long-lived token (3 years), token pasted straight from the Admin.
For OAuth details and request signing see the shopline-oauth skill.
Developer workflow
- Register on the Partner Portal (https://developer.myshopline.com/), create a developer store for testing.
- Create the app (public/custom) in the Developer Center to obtain APP Key and APP Secret (a.k.a. App Key / App Secret / appKey / appSecret).
- Implement OAuth (see
shopline-oauth), request the permission points (scopes) your app needs, e.g.read_products,write_products,read_orders. Keep the scope list minimal — broad scopes hurt App Store review. - Develop against a pinned API version; use the official SHOPLINE Developer MCP tools (
shopline-dev-mcpskill) to look up endpoints, parameter definitions and GraphQL schema instead of guessing. - Test with the developer store, then submit for review (public apps only; 1–2 business days, payments apps 3–5).
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 · 55 lines · 56 tokens per session scan A 1c3fedcfd20b
shopline-onboarding-dev is a skill published in the GitHub repository lunw/shopline-ai-toolkit-dsh (5 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 942 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
stripe-billing-subscriptions
Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.
customer-billing-ops
Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.
inventory-demand-planning
Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition…
customs-trade-compliance
Codified expertise for customs documentation, tariff classification, duty optimization, restricted party screening, and regulatory compliance across multiple jurisdictions. Informed by trade compliance specialists with 15+ years experience. Includes HS classification logic, Incoterms application, FTA utilization, and…
novel-reviewer
A review and editing workflow for existing novel chapters. It checks story logic, timelines, character states, unresolved clues, world rules, and writing style.
video-recap
A workflow that turns a supplied video into a Chinese narrated recap by combining video understanding, story planning, editing, voiceover, and final assembly.