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/create-runner-adapter/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/create-runner-adapter)<a href="https://agentmods.dev/skills/paperclipai/paperclip/create-runner-adapter"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/create-runner-adapter/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/create-runner-adapter"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/create-runner-adapter.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.00053 | $0.01114 |
| Opus 5.5 | $0.00021 | $0.00446 |
| Sonnet 5.5 | $0.00011 | $0.00223 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
create-runner-adapter 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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a native Runner adapter
Use this skill to add a harness to the new, native Paperclip Runner execution system. Here, adapter means the provider translation and launch integration behind a Runner harness driver. Preserve existing direct adapters and historical records as compatibility constraints; do not route this work through their package-authoring recipe or migrate agents as a side effect.
The complete procedure is the Runner integration playbook. Use its working templates for the release contract, capability inventory, acceptance ledger, and failure record. These repository files contain the decision rules and test criteria themselves. No private chat, task, prior campaign, or separate private repository is required. Source links identify code to inspect, not evidence that a new integration passed.
If this skill was installed separately, locate the target checkout from the
current workspace or git rev-parse --show-toplevel. Verify it contains
packages/paperclip-runner and tests/runner-e2e; resolve doc/ paths there.
Follow that checkout's AGENTS.md and scoped rules before editing.
Work sequence
- Define a finite release. Read playbook sections 1–3. Record the user outcome, first environment, supported platforms, setup/auth, required capabilities, selected acceptance model, spending limits, and delivery target. Keep the complete capability inventory separate from the release requirements.
- Investigate the actual harness. Use section 4. Inspect versioned official docs, native source or shipped code, real protocol traffic, and account/model behavior. Track every capability through native harness, wrapper, Runner, controller, and UI. Distinguish documented, observed, and qualified support.
- Prove one complete slice. Use sections 5–7. Establish exact model and instruction admission, scoped tools and credentials, then complete one real Paperclip task with independently verified output and physical cleanup. Exercise ordinary connect/save/reopen/Test/reconnect in the selected environment; check database constraints and account/model routing as well as driver execution.
- Complete the promised behavior. Use sections 8–10. Preserve rich events, durable human decisions, callback identity, recovery, cancellation, and terminal settlement. Keep provider-specific semantics in provider code.
- Prove delivery. Use section 11. Exercise clean installed packages and the agreed execution environment; verify the complete runtime closure and immutable image identity. A source checkout or startup probe is insufficient delivery proof.
- Qualify the release. Use sections 12–15. Begin with deterministic and real dependency checks, then run exact Product E2E cells through browser/server/DB/ Runner/provider. Section 12 includes a repository-contained test-authoring path. Freeze the candidate and retain original failures, cost coverage, and cleanup.
- Hand off an operable result. Use section 16 and the templates. Account for repository checks, exact passing evidence, remaining limits, installation, operation, and rollback. Keep merge, publish, deploy, and canary claims distinct.
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.
- 5d ago First seen · 87 lines · 53 tokens per session scan A 5d112873f396
create-runner-adapter is a skill published in the GitHub repository paperclipai/paperclip (107,044 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,114 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-20.
Other skills, from other repositories
agent-production-validator
Agent skill for production-validator - invoke with $agent-production-validator.
agent-tester
Agent skill for tester - invoke with $agent-tester.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
qa-testing
Generate and execute API and E2E tests with quality gate assessment.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
acceptance-criteria-gwt
Use when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases.