Prismer Cloud is an infrastructure layer for AI agents that provides shared learning, compressed context, persistent memory, collaboration, messaging, tasks, identity, and workspaces. It is for agents and the people building or using long-running agent systems that need information and outcomes to persist across sessions. The catalogue entries provide skills, hooks, agents, instructions, and a plugin for using Prismer Cloud.
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 Prismer-AI/PrismerCloud --skill doc-syncgit clone --depth 1 https://github.com/Prismer-AI/PrismerCloudWrote 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/prismer-ai/prismercloud/doc-sync)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/doc-sync"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/doc-sync/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/prismer-ai/prismercloud/doc-sync"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/doc-sync.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.00079 | $0.03192 |
| Opus 5.5 | $0.00032 | $0.01277 |
| Sonnet 5.5 | $0.00016 | $0.00638 |
| Haiku 4.5 | $0.00008 | $0.00319 |
Grade A, and why
doc-sync 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 19d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-sync
合入前把 Documentation-First 机械化：从 git diff 派生代码 delta，逐项核对该 delta 触发的文档义务是否已同步——CHANGELOG / docs/api/<domain> / CLAUDE.md / ROADMAP；SDK 包改动必须带对应 CHANGELOG + 版本文件对齐（apc/05 §2 S12 · apc/12 doc-sync 行）。
什么时候用：一个改动进合入门前，需要机械核对"该改的文档是不是都改了"，把"改了代码忘了 changelog / 忘了 api doc"这类漏挡在合入前。
铁律：代码 delta 来自真 git diff，不是假设。义务表的每条义务要写清"是 delta 的哪一部分触发的"——义务不是凭空列的清单，是 delta 推出来的。
工具契约（签名以此为准，先核后用）
| 命令 | 作用 | 备注 |
|---|---|---|
git diff --name-only [<base>..<head>] |
派生 delta：改了哪些文件 | 不带 range = working tree；分类的输入 |
git diff [-- <paths>] |
看具体改动内容（判 CHANGELOG 是否含本次条目） | — |
rg <stale-ref> docs/ CLAUDE.md |
猎 stale 引用（doc 里引了已删/改名的东西） | 出 path:line |
npx tsx scripts/apc-doc-sync.ts <taskId> |
机械门：改了 docs/sdk 但 diff 里不提 taskId → 非零 | exit 0 ok · 1 无 doc diff 或未提及 taskId · 2 用法错 |
sdk/build/version.sh --scope <s> <version> |
版本文件对齐（14 文件同步） | 写操作，只在真要 bump 时跑；核对用只读比对 |
cloud task verify-criterion <task-id> <criterion-id> --outcome <passed|failed|n/a|waived> |
上报 criterion | --outcome 恰好四值 |
apc-doc-sync.ts是机械门：它只校验"改动的 docs/sdk diff 里提到了 taskId"，是义务的必要非充分条件——它挡不住"改了 sdk 但没改 CHANGELOG"这种缺文件的漏，那要靠下面的义务表逐项核。两者叠加用。
义务表（delta → 必须同步的文档）
按 git diff --name-only 的命中，逐类推导文档义务：
| delta 命中 | 触发的文档义务 | 怎么核（satisfied 判据） |
|---|---|---|
sdk/<pkg>/src/**（SDK 包源码改） |
该包 sdk/<pkg>/CHANGELOG.md 有本次条目 + 14 版本文件对齐 |
changed 文件集里含该包 CHANGELOG；version.sh 只读比对版本一致 |
新增/改 endpoint（src/im/api/** / 路由） |
docs/api/<domain>.md 更新 + Last updated 日期 |
changed 含对应 domain doc |
prisma/schema*.prisma / src/im/sql/NNN_*.sql（schema/migration） |
docs/ARCHITECTURE.md / 相关 design doc + migration 编号连续 |
changed 含架构/design doc |
| 架构级行为变化（层/flag/大重构） | CLAUDE.md / docs/ROADMAP.md / docs/TODO.md |
changed 含对应文件 |
核心不变量（S12 唯一有意义的判据）：改了 SDK 包源码却没改该包 CHANGELOG = gap（缺义务）。这正是 apc/12 的正控/负控——缺 CHANGELOG 必须判缺，同步完整必须放行。
Procedure
1. 派生 delta（真 git diff，不假设）
git diff --name-only > /tmp/delta.txt # 或 <base>..<head>
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago First seen · 169 lines · 79 tokens per session scan A 2c1f4602fbe4
doc-sync is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,384 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 3,192 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-29.
Other skills, from other repositories
req-create
Create structured requirement documents from user ideas. Use when capturing new features, tasks, or user stories.
repository-onboarding
Orient an agent without loading the entire repository.
grooming
Shape ambiguous work into an agreed, executable plan. Use when the user asks to groom, scope, decompose, or prepare work before implementation.
grooming-evidence
Ground work grooming in existing product evidence. Use while shaping tasks from code, documentation, tracker state, and user feedback.
planning-with-files
Organize complex work with file-based planning artifacts such as taskplan.md, findings.md, and progress.md. Use when the user needs a multi-step task, project, or research effort broken down and tracked across many tool calls.
V3 Swarm Coordination
15-agent hierarchical mesh coordination for v3 implementation. Orchestrates parallel execution across security, core, and integration domains following 10 ADRs with 14-week timeline.