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 weshopai/weshop-dsh-plugin --skill open-weshop-2-0git clone --depth 1 https://github.com/weshopai/weshop-dsh-pluginWrote 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/weshopai/weshop-dsh-plugin/open-weshop-2-0)<a href="https://agentmods.dev/skills/weshopai/weshop-dsh-plugin/open-weshop-2-0"><img src="https://agentmods.dev/badge/skills/weshopai/weshop-dsh-plugin/open-weshop-2-0/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/weshopai/weshop-dsh-plugin/open-weshop-2-0"><img src="https://agentmods.dev/badge/skills/weshopai/weshop-dsh-plugin/open-weshop-2-0.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.00069 | $0.00185 |
| Opus 5.5 | $0.00028 | $0.00074 |
| Sonnet 5.5 | $0.00014 | $0.00037 |
| Haiku 4.5 | $0.00007 | $0.00018 |
Grade A, and why
open-weshop-2-0 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 5d 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.
What it actually says
Open weshop 2.0
- Start the bundled local server with
node ../../scripts/start-server.mjs, resolving the path relative to thisSKILL.mdfile. - Keep the server process running and read the
WESHOP_URLline from its output. - Open that exact URL in the Codex in-app browser.
- Report that weshop 2.0 is open.
Reuse an already-running server when available. Do not substitute an external browser unless the user explicitly requests it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · -3 lines · +33 tokens per session b941d8639126
- 1mo ago First seen · 17 lines · 36 tokens per session scan A 56f2f2acadf4
open-weshop-2-0 is a skill published in the GitHub repository weshopai/weshop-dsh-plugin (12 stars, last pushed 6d ago), licensed MIT. It adds 69 tokens to every session and 185 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-08-30.
Other skills, from other repositories
vigilante-create-issue
Help a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the $rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…
using-rn-dev-agent
Entry point for the rn-dev-agent plugin. Maps user intent to the right command, agent, or skill. Use at the START of any React Native development conversation. Triggers on "I want to build", "build a feature", "add a feature to the app", "test this", "something is broken", "fix the crash", "help with my React Native…