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-ingestgit 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-ingest)<a href="https://agentmods.dev/skills/paperclipai/paperclip/wiki-ingest"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/wiki-ingest/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-ingest"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/wiki-ingest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- 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.00061 | $0.00906 |
| Opus 5.5 | $0.00024 | $0.00362 |
| Sonnet 5.5 | $0.00012 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
wiki-ingest 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Ingest
Turn one source document into durable, interlinked wiki knowledge.
Inputs
- An operation issue with
operationType: "ingest"assigned to you. - A
raw/path mentioned in the issue body (always treatraw/as immutable). - The operation issue's target
wikiId,spaceSlug, and space root (otherwise stop and surface the missing config to the requester).
Workflow
- Read context first.
- Read the target space's
AGENTS.mdfor page conventions (filenames, frontmatter, voice, citation style). - Read the target space's
wiki/index.mdto see what already exists. - Read the target space's last ~20 entries of
wiki/log.mdto avoid re-ingesting a source or re-resolving a contradiction someone else already filed.
- Read the target space's
- Read the source end to end with
wiki_read_source, passing the operation issue'swikiIdandspaceSlug. Do not skim. Note the source's structure, claims, dates, and anything that contradicts existing pages. - Plan, then confirm — but only if the user is in the loop. If the operation came from a routine (no live user), proceed. If a user is asking interactively, summarise the 3–5 takeaways you intend to file and ask which to emphasise before writing.
- Write the source page at
wiki/sources/<slug>.md— ~300–800 words, frontmatter per the wiki schema, neutral voice, key claims with quoted excerpts where they carry weight. The source page is the canonical citation target for everything else this skill writes. - Update or create downstream pages in
entities/,concepts/, andsynthesis/. A typical ingest touches 5–15 pages; resist creating pages for ideas that only appear once. - Wire the cross-links. Every claim that comes from the source cites it as
(see [[wiki/sources/<slug>]]). Every entity / concept mentioned by name on more than one page links to its dedicated page. - Flag contradictions; do not silently overwrite. When new material disagrees with an existing page, append a
> ⚠ contradicted by [[wiki/sources/<slug>]] (YYYY-MM-DD)callout to the older page and note the conflict in the log. - Refresh
wiki/index.mdwith one-line summaries for any new pages. - Append a log entry in
wiki/log.md:## [YYYY-MM-DD] ingest | <source title> - source: raw/<filename> - new pages: [[...]], [[...]] - updated pages: [[...]], [[...]] - notes: <one-line synthesis or open question>
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 · 58 lines · 61 tokens per session scan A 476b87263892
wiki-ingest is a skill published in the GitHub repository paperclipai/paperclip (107,300 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 906 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
system-info
Get system information including CPU usage, memory, disk space, battery status, and network info. Read-only and safe to use.
agent-v3-memory-specialist
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist.
agent-swarm-memory-manager
Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
agent-memory-coordinator
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator.
memory-management
AgentDB memory system with HNSW vector search. Provides 150x-12,500x faster pattern retrieval, persistent storage, and semantic search capabilities for learning and knowledge management. Use when: need to store successful patterns, searching for similar solutions, semantic lookup of past work, learning from previous…