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.
git 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/rules/paperclipai/paperclip/acpx-profile-identity)<a href="https://agentmods.dev/rules/paperclipai/paperclip/acpx-profile-identity"><img src="https://agentmods.dev/badge/rules/paperclipai/paperclip/acpx-profile-identity/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/rules/paperclipai/paperclip/acpx-profile-identity"><img src="https://agentmods.dev/badge/rules/paperclipai/paperclip/acpx-profile-identity.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.00000 | $0.01026 |
| Opus 5.5 | $0.00000 | $0.00410 |
| Sonnet 5.5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
acpx-profile-identity 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACPX profile identity
Scope and purpose
This rule covers ACPX provider profiles, their release declarations and pins, the profile generator, the provider-pack contract registry, and the ACPX driver and provider code. Every ACPX harness (Claude, Codex, Copilot, Cursor, Grok, Pi, Antigravity and any new one) uses the same identity model, so a change behaves the same way for all of them.
The identity model
A provider profile in acpx-profiles.json has a version and a commandDigest.
Three things decide whether saved work and installed packs stay compatible:
| What changed | What carries it | Effect |
|---|---|---|
| The provider's upstream release: package versions, platform closures, a launcher shipped verbatim | The profile's commandDigest |
Saved sessions for that provider start fresh |
| The shared ACPX layer | The profile's acpxVersion and the Runner's ACPX patch in the pack contractDigest |
The same for every provider |
| A runner/pack contract: schemas, generated catalogs, Rust shapes and env keys | The provider pack's contractDigest |
Older image packs are not reused |
Ordinary Runner source changes, refactors and comments change none of these.
Required behavior
- Attest the upstream release. Declare each provider's attestation in
ACPX_RELEASE_ATTESTATIONS(scripts/acpx-release-attestations.mjs), using the kind that fits:installed-command,launcher,closureordeclaration. The digest binds only what a repackager copies verbatim from the upstream release, so the same release gives the same digest wherever the pack is built or installed. - Keep Paperclip source and the ACPX layer out of provider digests.
Runner/pack compatibility belongs to the
contractDigest. When Runner code and a pack must agree on a new field or behavior, declare it in a schema underprotocol/and generate the TypeScript, so the contract registry covers it. - Regenerate instead of hand-editing. After an upstream bump or a pin
change, run
pnpm --filter @paperclipai/paperclip-runner generate:acpx-profiles.check:acpx-profilesruns in the build and refuses a stale digest. - Keep the profile version. An upstream release changes the digest, not the
version. A new provider starts at version 1. Bump a version only to reset
every saved session for that provider on purpose, such as a change in saved
session semantics that exact admission cannot detect. Record the reason in
the PR and in the version table in
profile-compatibility.test.ts. - Keep earlier versions decodable. Saved inputs with any version from 1 through the current one decode, so recovery can refuse them. Launch and recovery admission require the exact current profile and digest.
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.
- 4d ago First seen · 73 lines · 0 tokens per session scan A 4b05dfca8324
acpx-profile-identity is a cursor rule published in the GitHub repository paperclipai/paperclip (110,831 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,026 tokens. 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-10-31.
Other cursor rules, from other repositories
kandev-pr-fixup
Kandev PR fixup workflow prompt for Cursor agents.
conventional-commits
Always use Conventional Commits for git commit messages.
database-schema
-- Users can belong to multiple ecosystems users (1) -----> (N) userecosystemmemberships (N) <----- (1) ecosystems.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.