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 danielrosehill/Claude-Image-Production-Plugin --skill workspace-setupgit clone --depth 1 https://github.com/danielrosehill/Claude-Image-Production-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/danielrosehill/claude-image-production-plugin/workspace-setup)<a href="https://agentmods.dev/skills/danielrosehill/claude-image-production-plugin/workspace-setup"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-image-production-plugin/workspace-setup/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/danielrosehill/claude-image-production-plugin/workspace-setup"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-image-production-plugin/workspace-setup.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.00075 | $0.00516 |
| Opus 5.5 | $0.00030 | $0.00206 |
| Sonnet 5.5 | $0.00015 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
workspace-setup 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 2mo 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
Image Workspace Setup
Register the folder the user treats as their image production workspace. Individual projects live as subfolders inside it.
Data store
${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/image-production/workspace.json
Do not write under ~/.claude/.
Procedure
1. Check for existing config
DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/image-production"
CONFIG="$DATA_DIR/workspace.json"
test -f "$CONFIG" && cat "$CONFIG"
If one exists, show the path and ask whether to keep or change it.
2. Ask the user
- Existing or new? — do they already have an image workspace, or should one be created?
- Path?
- Existing: ask for absolute path; verify with
test -d. - New: propose
~/media-workspaces/imagesas the default. Don't auto-create until the user confirms.
- Existing: ask for absolute path; verify with
3. (New only) Version control
Ask whether to git init the workspace. Default no — image libraries can be large.
4. Create + persist
mkdir -p "$DATA_DIR"
mkdir -p "<chosen-path>" # only if new
Write workspace.json:
{
"path": "/absolute/path",
"created": "<ISO-8601>",
"version_controlled": false,
"type": "image"
}
Use realpath to canonicalize.
5. Confirm
Print the registered path. Remind the user they can now say "open my image workspace" or "create a new image project".
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.
- 2mo ago First seen · 66 lines · 75 tokens per session scan A 97bb4e017c35
workspace-setup is a skill published in the GitHub repository danielrosehill/Claude-Image-Production-Plugin (21 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 516 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.
workspace-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| workspace-setupdanielrosehill/Claude-Image-Production-Plugin | Skill | 21 | yesterday | MIT | A | 75 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |