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 perniemann/pnCore --skill pn-paperclipgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-paperclip)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-paperclip"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-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.
<a href="https://agentmods.dev/skills/perniemann/pncore/pn-paperclip"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-paperclip.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.00076 | $0.00851 |
| Opus 5.5 | $0.00030 | $0.00340 |
| Sonnet 5.5 | $0.00015 | $0.00170 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
pn-paperclip 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 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.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paperclip Skill
Use this when working on tasks that originated from Paperclip or when you need to report workflow completion back to Paperclip.
When to use
- Tasks tied to Paperclip issues: checkout before work, comment, mark done, or sync status with governance rules.
- Any Paperclip API coordination (assignments, subtasks, identity) when domain coding is not the goal.
Output
- Correct sequencing of MCP tools (
paperclip_issue_checkout,paperclip_issue_comment,paperclip_issue_update) and HTTP calls for other endpoints per docs. - Issue state and comments updated in Paperclip when env vars (
PAPERCLIP_API_URL,PAPERCLIP_API_KEY, optionalPAPERCLIP_ISSUE_ID) are set.
pnCore Integration
When running inside Cursor with pnCore MCP:
- Checkout (start work): Call
paperclip_issue_checkoutbefore implementing. PassissueIdor rely onPAPERCLIP_ISSUE_ID. Do not usepaperclip_issue_updatewithin_progressfor that — checkout owns the transition. - Comments: Call
paperclip_issue_commentwithbody(markdown; @mentions supported per Paperclip docs).issueIdoptional whenPAPERCLIP_ISSUE_IDis set. - Mark issue done: Call
paperclip_issue_updatewithstatus: "done"and optionalcomment.issueIdoptional whenPAPERCLIP_ISSUE_IDis set. - Workflow complete: Terminal
workflow_stepinstructions include a Paperclip reminder whenPAPERCLIP_API_URLandPAPERCLIP_API_KEYare configured; callpaperclip_issue_update(and checkout earlier if you had not already).
Authentication
Env vars: PAPERCLIP_API_URL, PAPERCLIP_API_KEY. Optional: PAPERCLIP_ISSUE_ID (default issue for all three tools when issueId is omitted), PAPERCLIP_RUN_ID (sent as X-Paperclip-Run-Id), PAPERCLIP_AGENT_ID, PAPERCLIP_COMPANY_ID. All requests use Authorization: Bearer $PAPERCLIP_API_KEY.
Key Endpoints (Quick Reference)
| Action | Endpoint |
|---|---|
| My identity | GET /api/agents/me |
| My assignments | GET /api/companies/:companyId/issues?assigneeAgentId=:id&status=todo,in_progress,blocked |
| Checkout task | POST /api/issues/:issueId/checkout |
| Update task | PATCH /api/issues/:issueId (status, comment) |
| Add comment | POST /api/issues/:issueId/comments |
| Create subtask | POST /api/companies/:companyId/issues |
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 · 52 lines · 76 tokens per session scan A bbaa27dcfa1f
pn-paperclip is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 6d ago), licensed MIT. It adds 76 tokens to every session and 851 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
cocoharvest
Decompose an approved plan into parallel workstreams, assign specialist personas, classify stages as HITL or AFK (CocoLens), generate flow.json stages with checkpoints and dual-file state, and create per-stage prompt files. Includes adaptive parallelism, stall detection, shell identity injection, and consecutive…
plan
Enter the Plan phase of CocoBrew. Runs CocoSpec quality gate pre-flight, reads spec.md and discuss.md (if present), invokes Coco native plan mode as a mandatory gate, captures the approved plan to plan.md, creates initial flow.json template, and commits. Must have $spec completed first.
ops-demo
CocoOps demo mode activator — populates .cocoplus/ops/demo/ with realistic mock data and sets cocoplus.toml [demo] enabled = true. Invoked via $ops demo.
ops-dora
CocoOps DORA metrics — computes four DORA-adapted delivery metrics from Snowflake task history and git log. Extends the longitudinal delivery thesis through the skill-native CocoOps thesis workflow. Invoked via $ops dora.
ops-sprint
CocoOps sprint health — computes story velocity, burndown, and completion prediction from git log and sprint window config. Invoked via $ops sprint.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.