Open-Inspect is a hosted system that lets coding agents work on software tasks in background development environments. Teams use it to connect agents with repositories, communication tools, scheduled events, and parallel sandboxes. The catalogue contains add-ons associated with this system.
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 ColeMurray/background-agents --skill upload-screenshotgit clone --depth 1 https://github.com/ColeMurray/background-agentsWrote 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/colemurray/background-agents/upload-screenshot)<a href="https://agentmods.dev/skills/colemurray/background-agents/upload-screenshot"><img src="https://agentmods.dev/badge/skills/colemurray/background-agents/upload-screenshot.svg" alt="Measured on agentmods" 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.00020 | $0.00690 |
| Opus 5 | $0.00010 | $0.00345 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
upload-screenshot 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 7d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
upload-screenshot
Use this skill when you already have an image file on disk and need to upload it to the Open-Inspect
session. The image may be a screenshot captured by Playwright MCP or agent-browser, a generated
chart or diagram, a manual file, or output from another tool.
For the full browser-open + capture + upload workflow, use visual-verification instead.
Key Fact
upload-media is a bash command installed on PATH. Run it with your Bash tool. It is not an MCP
tool or a tool binding.
When To Use It
- Upload a screenshot that was already captured (e.g. via Playwright MCP)
- Upload a generated chart, graph, diagram, or other review image
- Upload an image file the user points you to
- The user says "upload the screenshot", "upload this image", or asks for an image they can review
Required Workflow
- Confirm the image file exists on disk.
- Run
upload-mediavia Bash with the file path and metadata flags. - Report the returned
artifactIdto the user.
Command
upload-media <file-path> \
--caption "Description of screenshot" \
--source-url "https://example.com" \
[--full-page] \
[--annotated] \
[--viewport '{"width":1512,"height":982}']
All flags except the file path are optional. Include whichever metadata you know:
--caption— what the screenshot shows--source-url— the URL that was captured--full-page— set if the screenshot is a full-page capture--annotated— set if the screenshot has annotations--viewport— JSON object with width and height of the viewport used
For generated images that do not depict a browser page, omit browser-specific flags such as
--source-url, --full-page, and --viewport.
Supported File Types
.png, .jpg / .jpeg, .webp
Success Criteria
The task is not complete until:
upload-mediareturned a JSON response containing anartifactId.- The
artifactIdis reported to the user. - The response states what was uploaded and the source URL (if known).
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.
- 7d ago First seen · 90 lines · 20 tokens per session scan A b958296faaec
upload-screenshot is a skill published in the GitHub repository ColeMurray/background-agents (2,733 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 690 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…