Borrowing it
Nothing to install: this file belongs to ctxpipe-ai/ctxpipe. 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/ctxpipe-ai/ctxpipe/main/.agents/skills/preview-env/workspaces/SKILL.mdgit clone --depth 1 https://github.com/ctxpipe-ai/ctxpipeWrote 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/ctxpipe-ai/ctxpipe/workspaces)<a href="https://agentmods.dev/skills/ctxpipe-ai/ctxpipe/workspaces"><img src="https://agentmods.dev/badge/skills/ctxpipe-ai/ctxpipe/workspaces/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/ctxpipe-ai/ctxpipe/workspaces"><img src="https://agentmods.dev/badge/skills/ctxpipe-ai/ctxpipe/workspaces.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.00028 | $0.01951 |
| Opus 5.5 | $0.00011 | $0.00780 |
| Sonnet 5.5 | $0.00006 | $0.00390 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
preview-env-workspaces 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 4d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
preview-env workspaces
Workspace identity and lifecycle. Harness is PASS; Workspace 1 exists from ONB-4. Flow format: run-setup. A Workspace has one workspace repository and zero or more linked repositories; a URL is the workspace repository of at most one Workspace per org.
WS-1 Open and switch panes
Requires ONB-4. Steps
- Open
{BASE_URL}/{orgSlug}/ws/{workspace1Slug}. - Click Files, Graph, Settings; then close the pane.
- Open any conversation (see CHAT-1) and click Diff.
- Return to the bare Workspace URL.
Expect (UI) the bare URL shows the composer (always a new composer) and the Workspace name; each tab sets pane=files, pane=graph, pane=settings; Diff sets pane=diff on a conversation URL only; closing removes pane.
Expect (backend) opening the bare URL creates no conversations row.
Budget 3 s / 10 s to compose; 1 s / 3 s per pane switch.
Evidence WS-1-1.png; trace of the workspace detail request.
WS-2 Read the settings chips
Requires WS-1. Steps
- Open Settings.
Expect (UI) write chip Writable, Read-only, or Checking write access; hydrate chip Hydrate ready, Hydrating, Hydrate pending, or Hydrate failed; display name and slug fields; the Linked repositories section (possibly empty). Record writeStatus and hydrateStatus for later flows.
Expect (backend) GET /{orgSlug}/api/v1/workspaces/{slug} returns the same writeStatus and hydrateStatus.
Budget 3 s / 10 s, Settings click to chips visible.
Evidence WS-2-1.png; JSON status fields.
WS-3 Add Workspace from the sidebar +
Requires WS-1; repo pe-{run-id}-ws2.
Steps
- Click the + next to the Workspaces label (
aria-label"Add Workspace"). - In the dialog, Select GitHub, search
pe-{run-id}-ws2, select it, click Create Workspace. - With two Workspaces, click Workspace 2's title, then Workspace 1's 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.
- 4d ago First seen · 99 lines · 28 tokens per session scan A 312598a322b6
preview-env-workspaces is a skill published in the GitHub repository ctxpipe-ai/ctxpipe (27 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,951 once invoked, about $0.0001 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-21.
Other skills, from other repositories
evidence-publish
Deliver a QA/evidence packet to a tracker or keep it local, behind an always-ask preview gate. Protocol for /orc:qa Phase 6, /orc:evidence, and any evidence-delivery step.
browser-journey-test
Validate user stories by simulating real user journeys in a live browser against deployed application. Activate after implementation to verify actual user experience against acceptance criteria, not just code logic.
sidekick-audit
Deterministic UI quality audit of a web page or a whole product — WCAG 2.2 A/AA accessibility (axe-core), Core Web Vitals (LCP/CLS), browser health (console errors, failed requests, mixed content) and tap-target size — reported dimensions-first, with confirmed-vs-uncertain findings clustered into root-cause families…
sidekick-test
Goal-based end-to-end UI testing that PROVES the outcome. Given a URL and a plain-language goal (e.g. 'sign up, create a project, and invite a teammate'), sidekick drives a real browser to do it and then verifies success with a DETERMINISTIC signal on the real page — the execution agent is never allowed to grade its…
agent-evaluation
A guide to measuring whether an AI agent works reliably on the tasks that matter. It covers repeatable test environments, program checks, human-like scoring rules, failure analysis, and experiments that separate model problems from system problems.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.