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-dev-mcpgit 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-dev-mcp)<a href="https://agentmods.dev/skills/lunw/shopline-ai-toolkit-dsh/shopline-dev-mcp"><img src="https://agentmods.dev/badge/skills/lunw/shopline-ai-toolkit-dsh/shopline-dev-mcp/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-dev-mcp"><img src="https://agentmods.dev/badge/skills/lunw/shopline-ai-toolkit-dsh/shopline-dev-mcp.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.00064 | $0.00966 |
| Opus 5 | $0.00032 | $0.00483 |
| Sonnet 5 | $0.00013 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
shopline-dev-mcp 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SHOPLINE Developer MCP Tools (via DSH)
The DSH plugin shopline-ai-toolkit-dsh bridges the official SHOPLINE Developer MCP server (@shoplineos/shopline-developer-mcp) through DSH's native MCP client. All its tools are available as native tools named mcp__shopline__<tool>. The server runs locally (stdio), requires no authentication, and needs Node.js >= 18.
Tool map (official server)
| DSH tool name | What it does | Use when |
|---|---|---|
mcp__shopline__shopline_readme |
README: dependencies & best practices of the MCP tools | Starting any SHOPLINE MCP session |
mcp__shopline__search_shopline_docs |
Search SHOPLINE developer docs | Broad questions ("how do webhooks work?", "product API") |
mcp__shopline__read_full_docs |
Full doc content by URL | You have a doc URL and need the complete text |
mcp__shopline__search_admin_rest_endpoints |
Search Admin REST endpoints | Finding the right REST path/resource |
mcp__shopline__get_rest_api_definition |
Full OpenAPI definition of a REST endpoint | Writing code against a REST endpoint |
mcp__shopline__get_admin_rest_endpoint_detail |
Detail: request params, response params, examples | Building a correct request/response contract |
mcp__shopline__get_graphql_schema |
Storefront GraphQL schema: Query/Mutation/Type | Schema lookups for Storefront GraphQL |
mcp__shopline__validate_graphql_codes |
Validate GraphQL code against the schema (syntax, deprecated, hallucinated fields) | Before shipping any generated GraphQL |
mcp__shopline__shopline_mcp_feedback |
Send feedback to SHOPLINE | Reporting doc/API issues |
Optional community server (sline.dev)
If enabled in cordis.patch.yml (row mcp-shopline-sline), the sline.dev MCP server adds mcp__sline__* tools:
| DSH tool name | What it does |
|---|---|
mcp__sline__learn_shopline_api |
Up-to-date API guidance + conversation context |
mcp__sline__search_docs_chunks |
Search sline.dev docs (chunked, may lack context) |
mcp__sline__fetch_full_docs |
Complete doc for an exact sline.dev path |
mcp__sline__introspect_admin_schema |
Introspect the Admin GraphQL schema (types, fields, queries, mutations) |
mcp__sline__validate_theme |
Validate Sline templates/theme files |
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 · 51 lines · 64 tokens per session scan A 35a396e384bb
shopline-dev-mcp is a skill published in the GitHub repository lunw/shopline-ai-toolkit-dsh (6 stars, last pushed 15d ago), licensed MIT. It adds 64 tokens to every session and 966 once invoked, about $0.0003 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
pipefy-introspection
Use this skill when you need to discover GraphQL type shapes, mutation signatures, enum values, or execute arbitrary GraphQL as a fallback. This is the first fallback tier (Tier 2) when dedicated MCP tools fail or don't exist for an operation. 7 MCP tools.
pipefy-api-fallback
Use this skill when an MCP tool fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier…
yao-process
Yao process execution expert. ALWAYS invoke this skill when the user needs to call a Yao process, query data models, run scripts, or check process permissions. Do not call processes without checking this skill first.
daytona-cloud-server
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
stripe-billing-subscriptions
Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.
kotlin-ktor-patterns
Ktor server patterns including routing DSL, plugins, authentication, Koin DI, kotlinx.serialization, WebSockets, and testApplication testing. Use when building a Ktor server — routing, plugins, auth, DI, serialization, or tests.