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-app-dev-doc-gapsgit 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-app-dev-doc-gaps)<a href="https://agentmods.dev/skills/lunw/shopline-ai-toolkit-dsh/shopline-app-dev-doc-gaps"><img src="https://agentmods.dev/badge/skills/lunw/shopline-ai-toolkit-dsh/shopline-app-dev-doc-gaps/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-app-dev-doc-gaps"><img src="https://agentmods.dev/badge/skills/lunw/shopline-ai-toolkit-dsh/shopline-app-dev-doc-gaps.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.00088 | $0.04850 |
| Opus 5 | $0.00044 | $0.02425 |
| Sonnet 5 | $0.00018 | $0.00970 |
| Haiku 4.5 | $0.00009 | $0.00485 |
Grade A, and why
shopline-app-dev-doc-gaps 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 11d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SHOPLINE App-Dev Doc Gaps（应用开发文档盲区补充）
This skill records SHOPLINE app-development platform behaviors that were not documented (or were documented incorrectly) on developer.shopline.com and cost real debugging time in a production-bound app project (Orbit PWA, a DTC PWA Enabler SHOPLINE app; verified across three debugging rounds, 2026-08-20 → 2026-08-22, including production install, billing and hardening). It is a supplement to the official docs for app development only — check the official docs first, and withdraw each entry as soon as the official docs cover it.
Scope & boundaries（适用范围与边界）
This skill covers ONLY app-development doc gaps:
| ✅ In scope (app development) | ❌ Out of scope |
|---|---|
| SHOPLINE CLI local development contract (process configs, env semantics, install probe, injected assets) | Theme development (Sline/Liquid templates, theme structure) |
| OAuth callback & install contract (callback path, admin-proxy callback, per-visit install params, handle resolution) | Storefront pure-frontend issues (SDK internals, cache strategies) |
| Embedded admin integration (context routing, session handle, App Bridge wiring & auth protocol) | The SHOPLINE Developer MCP tools themselves |
| App permission point mapping (OpenAPI scope → endpoint requirements) | Generic web knowledge (cookies, CORS, HTTPS, layout) |
Boundary rules:
- A pitfall stays ONLY if it is platform-level and app-dev-related; project-internal conventions and generic web knowledge are deliberately excluded.
- If a future gap belongs to theme dev or storefront, create a separate
shopline-theme-doc-gaps-style skill instead of extending this one. - When in doubt, exclude: this skill must stay a small, mechanical delta over the docs.
Withdrawal policy (撤回策略)
- Every entry has a verified date and a row in the coverage table.
- When official documentation starts covering an entry, delete that entry from this
skill and flip its table row to
fixed → withdrawn. - Do not merge this knowledge into the other
shopline-*skills: those mirror documented behavior; this one is the removable delta. - Track withdrawals in the repo README ("Doc gap status") so reviewers can audit.
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.
- 11d ago First seen · 200 lines · 0 tokens per session scan A d138ce68469a
shopline-app-dev-doc-gaps is a skill published in the GitHub repository lunw/shopline-ai-toolkit-dsh (6 stars, last pushed 15d ago), licensed MIT. It adds 88 tokens to every session and 4,850 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-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…
style
Luxe fashion-commerce editorial design with a deep-indigo canvas, oversized numerals, large image-led storytelling, rounded capsules/cards, and restrained monochrome accents.
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…