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.
npx skills add aronprins/paperclip-cli --skill paperclip-cligit clone --depth 1 https://github.com/aronprins/paperclip-cliWrote 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/aronprins/paperclip-cli/paperclip-cli)<a href="https://agentmods.dev/skills/aronprins/paperclip-cli/paperclip-cli"><img src="https://agentmods.dev/badge/skills/aronprins/paperclip-cli/paperclip-cli/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/aronprins/paperclip-cli/paperclip-cli"><img src="https://agentmods.dev/badge/skills/aronprins/paperclip-cli/paperclip-cli.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.00138 | $0.03639 |
| Opus 5.5 | $0.00055 | $0.01456 |
| Sonnet 5.5 | $0.00028 | $0.00728 |
| Haiku 4.5 | $0.00014 | $0.00364 |
Grade A, and why
paperclip-cli 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 1mo 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 -s "$PAPERCLIP_API_URL/api/health" # is the server even up How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating the Paperclip CLI (paperclipai)
Core mental model
- Two layers. Setup commands (
onboard,doctor,configure,runwith no subcommand,db:backup,worktree*,env-lab) operate on local config/DB under~/.paperclipand need no credential. Control-plane commands (everything else: company, issue, agent, run<sub>, routine, budget, ...) are HTTP clients for the server API and need an API base + credential. - The CLI never runs the model. Agent work executes server-side in the Paperclip runtime/adapters. The CLI triggers (
agent wake,heartbeat run) and observes (run *). You conduct; the server computes. Sole exception:agent local-clisets up your machine so a local AI acts as that agent and reports back via the API. - Two personas: board operator (instance-wide authority; bootstraps, builds the org, mints credentials) and agent (scoped to exactly one company + one agent). Matching credentials: board API token (
token board create, named/expirable/revocable) and agent API key (token agent create, plaintext shown once). - API base resolution, first match wins:
--api-base→PAPERCLIP_API_URL→ profileapiBase→ local config port →http://localhost:3100. - Context profiles (
~/.paperclip/context.json) store defaults per profile: apiBase, companyId, persona, agentId. They storeapiKeyEnvVarName— the name of an env var, never a plaintext secret. The token stays in your environment.
Quick environment check
Run these first to see what you already have:
env | grep '^PAPERCLIP_' # PAPERCLIP_API_URL / _COMPANY_ID / _AGENT_ID / _API_KEY already exported?
paperclipai context show # active profile: apiBase, companyId, persona, apiKeyEnvVarName, contextPath
paperclipai whoami --json # which identity the current credential resolves to
curl -s "$PAPERCLIP_API_URL/api/health" # is the server even up
If the four PAPERCLIP_* env vars are set, you are almost certainly running as an agent persona already — operate with them directly, no profile needed.
What ships with it
9 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.
- references/agents-and-prompts.md 18 KB
- references/auth-and-context.md 20 KB
- references/extension.md 18 KB
- references/observability-and-cost.md 14 KB
- references/org.md 20 KB
- references/platform.md 18 KB
- references/runs-and-routines.md 18 KB
- references/scripting-and-automation.md 14 KB
- references/setup-and-instance.md 19 KB
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.
- 1mo ago First seen · 148 lines · 138 tokens per session scan A 8a8fe8a705a1
paperclip-cli is a skill published in the GitHub repository aronprins/paperclip-cli (18 stars, last pushed 4mo ago), licensed MIT. It adds 138 tokens to every session and 3,639 once invoked, about $0.0006 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…