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 wiki-querygit 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/wiki-query)<a href="https://agentmods.dev/skills/paperclipai/paperclip/wiki-query"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/wiki-query/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/wiki-query"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/wiki-query.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.00041 | $0.00645 |
| Opus 5 | $0.00020 | $0.00322 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
wiki-query 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Query
Answer a question from what the wiki actually contains, with citations.
Inputs
- An operation issue with
operationType: "query"and the question in the body. - The operation issue's target
wikiId,spaceSlug, and space root.
Workflow
- Open the target space's
wiki/index.mdfirst — it is the navigation aid. Identify candidate pages. - Read the candidate pages end to end with
wiki_read_page, always passing the operation issue'swikiIdandspaceSlug. Follow[[wiki-links]]to neighbouring pages when the question spans entities or concepts. - Inspect raw sources when a wiki page's claim feels thin. The wiki points to
raw/precisely so you can verify before answering. Usewiki_read_source. - Answer the question in the operation issue thread. Structure:
- Direct answer first, in 1–4 sentences.
- Then the supporting facts as bullet points, each with an inline citation:
(see [[wiki/concepts/managed-resources]])or(see raw/<filename>). - If you needed to read a raw source the wiki did not summarise, name that as a gap.
- Decide whether the answer is durable. If the question forced you to do real synthesis (a comparison, a tradeoff, a definition of something that isn't already a page), offer to file it under
wiki/synthesis/<slug>.md. Do not write the synthesis page silently — it is opt-in. If the user accepts, write the page, link it fromwiki/index.md, and append aquery | filed synthesislog entry. - When the wiki cannot answer, say so plainly. Suggest a source the user should ingest, a Paperclip project that would help if distilled, or a web lookup. Never bluff.
Voice
- Lead with the answer.
- Cite as you go, not in a footnote block at the end.
- Use the wiki's terse, factual voice. The query response is itself a candidate for filing into
wiki/synthesis/.
Verification
Before closing the operation issue:
- Every claim in the answer cites a wiki page or raw source.
- If the wiki was insufficient, that is stated directly with a concrete next step (ingest source X, distill project Y, web search Z).
- If you wrote a synthesis page,
wiki/index.mdlists it andwiki/log.mdhas aquery | filed synthesisentry. - No file under
raw/was modified.
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 · 45 lines · 41 tokens per session scan A 73332d0b2d86
wiki-query is a skill published in the GitHub repository paperclipai/paperclip (80,206 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 645 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…