Open SWE is an open-source software factory that gives coding tasks to an asynchronous agent, which investigates repositories, changes code, validates the results, and delivers pull requests. Engineering teams use it to automate code changes, reviews, CI follow-up, and related repository work from dashboards and connected tools.
Borrowing it
Nothing to install: this file belongs to langchain-ai/open-swe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/langchain-ai/open-swe/main/.claude/skills/dashboard-preview/SKILL.mdgit clone --depth 1 https://github.com/langchain-ai/open-sweWrote 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/langchain-ai/open-swe/dashboard-preview)<a href="https://agentmods.dev/skills/langchain-ai/open-swe/dashboard-preview"><img src="https://agentmods.dev/badge/skills/langchain-ai/open-swe/dashboard-preview/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/langchain-ai/open-swe/dashboard-preview"><img src="https://agentmods.dev/badge/skills/langchain-ai/open-swe/dashboard-preview.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.00055 | $0.00924 |
| Opus 5.5 | $0.00022 | $0.00370 |
| Sonnet 5.5 | $0.00011 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
dashboard-preview 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 yesterday.
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.
Dashboard against preview
pnpm run dev:prod serves this checkout's ui/ from Vite and proxies the API to a deployment with a real session, so every page shows real threads.
Point it at preview, never production:
DASHBOARD_API_URL=https://open-swe-preview-cc53e8fbe667565d843d0843f84ee92c.us.langgraph.app pnpm run dev:prod
The first run opens the user's browser for a GitHub handoff.
When they are signed in to GitHub it completes on its own, and the session is cached in ~/.cache/open-swe/dev-session.json for a week.
If pnpm fails with No version is set for shim: pnpm, run it as mise exec pnpm@<version> -- pnpm run dev:prod, taking the version from packageManager in package.json.
Browser pane
The in-app Browser pane needs a launch configuration that starts the server; one that only names a URL is refused.
Write .claude/launch.json (leave it uncommitted), then preview_start dashboard-preview:
{
"version": "0.0.1",
"configurations": [
{
"name": "dashboard-preview",
"runtimeExecutable": "pnpm",
"runtimeArgs": ["run", "dev:prod"],
"env": { "DASHBOARD_API_URL": "https://open-swe-preview-cc53e8fbe667565d843d0843f84ee92c.us.langgraph.app" },
"port": 3000
}
]
}
Vite holds port 3000 strictly: stop any dev:prod you started from Bash first.
The ego-browser skill works too, and it carries the user's real login for both preview and production.
The session is real
Reading is free. A message sent from the composer starts a real run, and opening a pull request's review page creates its chat thread. Ask the user before either.
Finding a thread to test on
Only threads with transcript: "v2" read the transcript log; older ones answer /transcript with 404 and go through the SDK stream.
Rank candidates by size from the page:
const { items } = await (await fetch("/dashboard/api/threads/page?limit=40")).json()
for (const t of items.filter((t) => t.transcript === "v2")) {
const s = await (await fetch(`/dashboard/api/threads/${t.id}/transcript`)).json()
console.log(t.id, t.status, s.tool_calls.length, t.title)
}
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.
- yesterday Changed · -8 lines f58668e90282
- 3d ago First seen · 98 lines · 55 tokens per session scan A 0398ce185c12
dashboard-preview is a skill published in the GitHub repository langchain-ai/open-swe (11,133 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 924 once invoked, about $0.0002 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-10-26.
Other skills, from other repositories
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
opencli
Blazing fast Rust CLI tool that turns 55+ websites into CLI interfaces, reusing Chrome's login state. Zero credentials needed. Single 4.7MB binary, zero runtime dependencies.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
blocked-page-recovery
Use when a fetch fails: 403/429, paywall, WAF, bot wall.
playwright
Use when the task requires capturing or automating a real browser from the terminal.
langbot-plugin-dev
Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invokellm, getllmmodels, sendmessage, plugin storage)…