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.
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 paperclipai/paperclip --skill index-refreshgit 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/index-refresh)<a href="https://agentmods.dev/skills/paperclipai/paperclip/index-refresh"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/index-refresh/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/index-refresh"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/index-refresh.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00043 | $0.00950 |
| Opus 5 | $0.00022 | $0.00475 |
| Sonnet 5 | $0.00009 | $0.00190 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
index-refresh 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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Index Refresh
Keep wiki/index.md accurate and scannable. The index is the maintainer's first stop for navigation — its quality determines how cheap every subsequent operation becomes.
Inputs
- An operation issue with
operationType: "index"(or theindex-refreshroutine title). - The operation issue's target
wikiId,spaceSlug, and space root. Refresh only that space unless the issue explicitly says this is a multi-space sweep.
Workflow
- Read the target space's
wiki/index.mdas it currently stands. - Walk the target space's
wiki/.wiki/projects/<slug>/standup.mdentries are current-state companions for durablewiki/projects/<slug>/index.mdpages; index them only as links attached to the matching project entry. Walkwiki/by category (sources/,projects/,entities/,concepts/,synthesis/, plus any custom subdirectories the wiki schema added). - Read the target space's last ~50 entries of
wiki/log.mdto spot pages that were created or substantially changed but never made it to the index. - Per category, produce sorted entries of the form:
The summary is one factual sentence pulled from the page's first paragraph or its title. No status, no datestamps in the index — those belong in the page itself or in the log.- [[<path>]] — <one-line summary> - Drop entries whose page no longer exists. Note the deletion in the log:
## [YYYY-MM-DD] index-refresh | reconciled - removed: [[wiki/old-page]] (page deleted) - added: [[wiki/new-page]] — <summary> - Add entries for pages that exist on disk but were missing from the index. Skip
wiki/log.mdandwiki/index.mdthemselves. For standalonewiki/projects/<slug>/standup.mdwithout a matching durable project page, add it under Projects and flag it for later durable-page distillation. - Write project entries editorially. The Projects section should group work by the project's concept and purpose, not by issue ids, dates, statuses, UUIDs, or source metadata. Link task identifiers only as supporting evidence.
- Preserve custom categories. If the wiki has added e.g.
wiki/papers/orwiki/runbooks/, keep its index section. Do not collapse to the default five categories. - Append a log entry with counts:
If the index was already accurate, the log entry says## [YYYY-MM-DD] index-refresh | added=N removed=M - operation issue: <issue identifier>added=0 removed=0— still write it so future audits can see the run happened.
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.
- 9d ago First seen · 66 lines · 43 tokens per session scan A 0d015e9986e0
index-refresh is a skill published in the GitHub repository paperclipai/paperclip (80,206 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 950 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…