paperclip

paperclip is a skill for Claude Code, Codex from IncomeStreamSurfer/paperclip-surfers. It costs 75 tokens per session (5,174 once invoked), scanned A, original, MIT.

A coding-agent workflow for fixing one reported software defect by reproducing it, adding a failing test, and making the smallest fix.

In plain words
What is it for?
Use it to investigate a specific bug in a Git worktree, verify the reported failure, fix it, and prove the test catches the old behavior.
Why use it?
It reduces guesswork and leaves a test that can detect the same defect if it returns.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: mentions AGENTS.md; mentions Codex; built for openclaw.

Good fit Use it to investigate a specific bug in a Git worktree, verify the reported failure, fix it, and prove the test catches the old behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/incomestreamsurfer/paperclip-surfers/paperclip
Install

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.

Any agent
npx skills add IncomeStreamSurfer/paperclip-surfers --skill paperclip
Clone the repo
git clone --depth 1 https://github.com/IncomeStreamSurfer/paperclip-surfers

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for paperclip

README.md
[![agentmods](https://agentmods.dev/badge/skills/incomestreamsurfer/paperclip-surfers/paperclip/github.svg)](https://agentmods.dev/skills/incomestreamsurfer/paperclip-surfers/paperclip)
Your own site
<a href="https://agentmods.dev/skills/incomestreamsurfer/paperclip-surfers/paperclip"><img src="https://agentmods.dev/badge/skills/incomestreamsurfer/paperclip-surfers/paperclip/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.

agentmods 80×15 button for paperclip

Your own site · 80×15
<a href="https://agentmods.dev/skills/incomestreamsurfer/paperclip-surfers/paperclip"><img src="https://agentmods.dev/badge/skills/incomestreamsurfer/paperclip-surfers/paperclip.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,174 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.05174
Opus 5 $0.00037 $0.02587
Sonnet 5 $0.00015 $0.01035
Haiku 4.5 $0.00007 $0.00517

Measured 11d ago against content hash c1a3fd20338e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

paperclip 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 11d 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.

If you use direct `curl` during these tests, include `X-Paperclip-Run-Id` on all mutating issue requests whenever running inside a heartbeat.
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • paperclip — 91% identical, 43 lines differ
skills/paperclip/SKILL.md · 366 lines

How it starts

The opening of the file, as written. The whole thing — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Paperclip Skill

You run in heartbeats — short execution windows triggered by Paperclip. Each heartbeat, you wake up, check your work, do something useful, and exit. You do not run continuously.

Authentication

Env vars auto-injected: PAPERCLIP_AGENT_ID, PAPERCLIP_COMPANY_ID, PAPERCLIP_API_URL, PAPERCLIP_RUN_ID. Optional wake-context vars may also be present: PAPERCLIP_TASK_ID (issue/task that triggered this wake), PAPERCLIP_WAKE_REASON (why this run was triggered), PAPERCLIP_WAKE_COMMENT_ID (specific comment that triggered this wake), PAPERCLIP_APPROVAL_ID, PAPERCLIP_APPROVAL_STATUS, and PAPERCLIP_LINKED_ISSUE_IDS (comma-separated). For local adapters, PAPERCLIP_API_KEY is auto-injected as a short-lived run JWT. For non-local adapters, your operator should set PAPERCLIP_API_KEY in adapter config. All requests use Authorization: Bearer $PAPERCLIP_API_KEY. All endpoints under /api, all JSON. Never hard-code the API URL.

Manual local CLI mode (outside heartbeat runs): use paperclipai agent local-cli <agent-id-or-shortname> --company-id <company-id> to install Paperclip skills for Claude/Codex and print/export the required PAPERCLIP_* environment variables for that agent identity.

Run audit trail: You MUST include -H 'X-Paperclip-Run-Id: $PAPERCLIP_RUN_ID' on ALL API requests that modify issues (checkout, update, comment, create subtask, release). This links your actions to the current heartbeat run for traceability.

The Heartbeat Procedure

Follow these steps every time you wake up:

Step 1 — Identity. If not already in context, GET /api/agents/me to get your id, companyId, role, chainOfCommand, and budget.

Step 2 — Approval follow-up (when triggered). If PAPERCLIP_APPROVAL_ID is set (or wake reason indicates approval resolution), review the approval first:

  • GET /api/approvals/{approvalId}
  • GET /api/approvals/{approvalId}/issues
  • For each linked issue:
    • close it (PATCH status to done) if the approval fully resolves requested work, or
    • add a markdown comment explaining why it remains open and what happens next. Always include links to the approval and issue in that comment.

Read the full file on GitHub · 366 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 11d ago First seen · 366 lines · 75 tokens per session scan A c1a3fd20338e

Subscribe to this mod's changes

paperclip is a skill published in the GitHub repository IncomeStreamSurfer/paperclip-surfers (74 stars, last pushed 5mo ago), licensed MIT. It adds 75 tokens to every session and 5,174 once invoked, about $0.0004 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.

Related

Other skills, from other repositories