Paperclip is a Node.js server and React application for coordinating AI agents as a business team, with goals, organizational roles, budgets, governance, and work tracking in one interface. It is used by people managing multiple agents or autonomous agent organizations across tools such as OpenClaw, Claude Code, Codex, and Cursor. The catalogue includes skills, agents, an MCP add-on, and an instruction for working with Paperclip.
Borrowing it
Nothing to install: this file belongs to paperclipai/paperclip. 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/paperclipai/paperclip/master/.agents/skills/paperclip-dev-workspace-run-verify-fix/SKILL.mdgit clone --depth 1 https://github.com/paperclipai/paperclipWrote 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/paperclipai/paperclip/paperclip-dev-workspace-run-verify-fix)<a href="https://agentmods.dev/skills/paperclipai/paperclip/paperclip-dev-workspace-run-verify-fix"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/paperclip-dev-workspace-run-verify-fix/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/paperclipai/paperclip/paperclip-dev-workspace-run-verify-fix"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/paperclip-dev-workspace-run-verify-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 117 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 182 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium MCP Rug Pull · line 211 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00058 | $0.04945 |
| Opus 5 | $0.00029 | $0.02472 |
| Sonnet 5 | $0.00012 | $0.00989 |
| Haiku 4.5 | $0.00006 | $0.00494 |
Grade A, and why
paperclip-dev-workspace-run-verify-fix scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -X POST \ How it starts
The opening of the file, as written. The whole thing — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paperclip Dev Workspace Run / Verify / Fix
This skill is for Paperclip-specific development workspaces whose service is
started through project execution workspace runtime services, typically a
worktree service such as paperclip-dev.
Success means all of these are true:
- the service was started through the normal managed runtime path, not a detached workaround
- the worktree database is a full bootstrapped isolated clone of the primary instance database
/api/healthreturnsstatus: okandbootstrapStatus: ready- the root page returns
200and does not show the first-admin setup gate - the board user can log in with their normal dev credentials
- the app shows populated cloned data, not only a manually copied auth user
- the main control plane shows the service as
running/healthywith the expected URL - the served workspace app also knows about that service and shows it as
running/healthy - the process that owns the service port really belongs to the target
workspace:
readlink /proc/<pid>/cwdresolves inside the target worktree, not a sibling workspace
If any item fails, keep fixing. Do not mark the issue done because one probe passed.
Hard rules
- The master checkout
/srv/paperclip/home/paperclipai/paperclip(the primary repo with the real instance.env) is never a workspace repair target. Never point a worktree runtime service at it, nevergit worktree addinto it or under<master>/.paperclip/worktrees/, and never edit its.envwhile repairing a workspace. Managed workspaces run in their own folders, for example~/.paperclip-worktrees/instances/<slug>/…. - Never trust a
running/healthyruntime row or a passing/api/healthalone. Theservice:paperclip-devport is pinned in service config, so a sibling workspace's process can own the port and still answer health checks. Confirm the port owner's real cwd (readlink /proc/<pid>/cwd) before and after every repair; the runtime row's recordedcwdandpidcan be fabricated by port adoption. - Read
doc/DEVELOPING.mdbefore running Paperclip CLI, dev server, worktree, database, build, or test commands. - Use the Paperclip CLI and API as the source of truth for worktree and
database operations. Do not use
psql, raw embedded-Postgres commands, or ad hoc row copying for the normal fix path. - Do not manually copy only auth rows as the final fix. That proves login, but it does not prove the isolated workspace has the full bootstrapped database.
- Prefer managed runtime start/stop routes over
pnpm devor detached shell processes when the task is about a reusable workspace service. - Avoid destructive git or database actions. Preserve user changes in the worktree.
- Run the smallest verification that proves the repair. Add focused tests only when code changed.
- Leave an issue comment with root cause, exact fix, verification, and any commit link. Set a clear final status.
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.
- 12d ago First seen · 518 lines · 58 tokens per session scan A a3b8cb9be7a8
paperclip-dev-workspace-run-verify-fix is a skill published in the GitHub repository paperclipai/paperclip (80,385 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 4,945 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.