inspect-weshop-canvas

inspect-weshop-canvas is a skill for Codex from weshopai/weshop-dsh-plugin. It costs 82 tokens per session (1,235 once invoked), scanned A, original, MIT.

A tool for working with the current WeShop canvas, a shared workspace for image, video, audio, and text materials. It can inspect canvas content and handle requested generation or image-editing workflows.

In plain words
What is it for?
Use it to inspect canvas results, create or transform images, upscale them, derive prompts from them, edit them locally, and publish generated media or text to the canvas.
Why use it?
It keeps generated or edited materials connected to the canvas and requires completed outputs to be published there before the task is considered finished.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex; $skill-name invocation.

Good fit Use it to inspect canvas results, create or transform images, upscale them, derive prompts from them, edit them locally, and publish generated media or text to the canvas.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/weshopai/weshop-dsh-plugin/inspect-weshop-canvas
Install

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.

Any agent
npx skills add weshopai/weshop-dsh-plugin --skill inspect-weshop-canvas
Clone the repo
git clone --depth 1 https://github.com/weshopai/weshop-dsh-plugin

Made for: Codex.

Wrote 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.

agentmods badge for inspect-weshop-canvas

README.md
[![agentmods](https://agentmods.dev/badge/skills/weshopai/weshop-dsh-plugin/inspect-weshop-canvas/github.svg)](https://agentmods.dev/skills/weshopai/weshop-dsh-plugin/inspect-weshop-canvas)
Your own site
<a href="https://agentmods.dev/skills/weshopai/weshop-dsh-plugin/inspect-weshop-canvas"><img src="https://agentmods.dev/badge/skills/weshopai/weshop-dsh-plugin/inspect-weshop-canvas/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.

agentmods 80×15 button for inspect-weshop-canvas

Your own site · 80×15
<a href="https://agentmods.dev/skills/weshopai/weshop-dsh-plugin/inspect-weshop-canvas"><img src="https://agentmods.dev/badge/skills/weshopai/weshop-dsh-plugin/inspect-weshop-canvas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,235 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.01235
Opus 5.5 $0.00033 $0.00494
Sonnet 5.5 $0.00016 $0.00247
Haiku 4.5 $0.00008 $0.00123

Measured 5d ago against content hash 74c15eb0548c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

inspect-weshop-canvas 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.

plugins/weshop-2-0/skills/inspect-weshop-canvas/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Inspect weshop Canvas

Non-negotiable insertion rule

  • Add in the webpage is exclusively a human-facing material importer. Never click it, open its file chooser, or use browser automation to insert a generated output.
  • Every successful image MUST be inserted with weshop_canvas_publish_result. Publish generated video, audio, or text with weshop_canvas_publish_asset and the matching mediaType before replying that the task is complete.
  • Publishing the result is part of generation completion, not an optional follow-up step. Do not ask the user to add it manually.
  • If publishing fails, report the failure and retry the canvas tool; do not fall back to the webpage Add button.

Intent and command routing

Invoke $weshop-openapi-skill before choosing any WeShop command. That skill is the sole authority for intent compilation, command classification, commercial workflow selection, foundation-model routing, prompt recipes, speed/quality selection, run planning, and acceptance checks. This canvas skill only supplies selected assets and publishes outcomes.

Visible execution progress

Use weshop_canvas_report_progress at meaningful transitions so the canvas exposes concise, verifiable status—not private chain-of-thought. Set one stable startedAt timestamp for the task and include a monotonic percent:

  1. interpreting (~8%): one-sentence understanding plus outputPlan.
  2. researching (~12–20%, only when required): report the platform/market/source focus and that current specifications or references are being checked.
  3. planning (~22%): selected WeShop commercial workflow or model and why it fits in a short factual summary.
  4. prompt-ready (~32%): set promptStatus to “已完成”; summarize the prompt constraints without dumping hidden reasoning.
  5. generating (35–85%): report the active model and expected output count. Update only when the API status meaningfully changes.
  6. publishing (~92%): report that completed files are being added automatically.
  7. complete (100%) or error: report the concrete outcome.

Read the full file on GitHub · 67 lines

Files

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.

Changes

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.

  1. 5d ago Changed · +3 lines · +1 tokens per session 74c15eb0548c
  2. 1mo ago First seen · 64 lines · 81 tokens per session scan A d032185c36c7

Subscribe to this mod's changes

inspect-weshop-canvas is a skill published in the GitHub repository weshopai/weshop-dsh-plugin (12 stars, last pushed 6d ago), licensed MIT. It adds 82 tokens to every session and 1,235 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.

Related

Other skills, from other repositories

vigilante-create-issue

Help a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.

aliengiraffe/vigilante · 25 tokens

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…

Lykhoyda/rn-dev-agent · 98 tokens

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…

Lykhoyda/rn-dev-agent · 86 tokens

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…

Lykhoyda/rn-dev-agent · 106 tokens

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…

Lykhoyda/rn-dev-agent · 91 tokens

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…

Lykhoyda/rn-dev-agent · 92 tokens