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 impact-tracegit 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/impact-trace)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/impact-trace"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/impact-trace/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/impact-trace"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/impact-trace.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.00060 | $0.03073 |
| Opus 5.5 | $0.00024 | $0.01229 |
| Sonnet 5.5 | $0.00012 | $0.00615 |
| Haiku 4.5 | $0.00006 | $0.00307 |
Grade A, and why
impact-trace 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 17d 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.
impact-trace
给定一个改动点（函数 / 类型 / endpoint / SQL 列），产出它的真实影响面（受影响的调用方 / 契约消费者 / 持久化写入 / 双 Prisma schema / daemon-SDK 镜像 / skill-role 引用）+ 由此推导的回归测试范围（apc/05 §2 S2 · apc/12 impact-trace 行）。
什么时候用：一个 bugfix / feature 改完，进 review 前需要知道"改这一处会波及哪些地方、要回归哪些层"；或评审要判断改动的 blast radius。
铁律：影响表的每一行都必须有 grep/search 证据（path+line）。凭记忆或推理写"这里应该会用到"是开卷考试——本 skill 的产出只认真实搜索命中。你自己不是 ground truth，rg 的命中集才是。
工具契约（签名以此为准，先核后用）
| 命令 | 作用 | 备注 |
|---|---|---|
rg <pattern> [path] -n |
主力搜索：直接调用方 / 契约消费者 / 引用点 | -n 出行号（证据必须带行号）；-l 只列文件；-t ts 限类型 |
rg -c <pattern> |
命中计数（核对"没漏"用） | 计数对不上就是漏搜 |
cloud code grep <pattern> --repo <abs> [--glob '*.ts'] |
白名单 repo 内搜索，输出 JSON [{path,line,snippet,sha256}] |
仅 PRISMER_WORKSPACE_ROOT 或 ~/.prismer/agents/<id>/scratch 内；出带 sha 的可引用片段。--glob 只支持 *.ext 形态 |
rg是本机主力；cloud code grep用于要产出可引用证据片段（带 sha256）时。两者的命中集应当一致——不一致就查是不是路径白名单/glob 把一部分挡在外面了。- 不要用单文件 grep 命中当全貌（memory
feedback_grep_full_range_for_seq_audit）。搜完要核计数：rg -c的总数 == 影响表行数（去掉 N/A 维度），对不上就是漏了。
六维影响面（逐维搜，缺一维要么有证据要么写 N/A 理由）
改动点波及面按六维穷举。任一维标 N/A 必须写理由；双 Prisma 维度永远不许静默省略（apc/12 负控：缺双 Prisma 维且无 N/A 理由 → 校验拒绝）。
| # | 维度 | 怎么搜（示例） | 找什么 |
|---|---|---|---|
| 1 | 直接调用方 | rg '\b<name>\b' -n -t ts |
谁 import / 调用了这个符号 |
| 2 | 契约消费者（API/wire） | rg '<endpoint-path>|<event-code>|<rpc-name>' -n |
HTTP 路由消费者、SDK 类型、wire 帧的两端 |
| 3 | 持久化写入 | rg '<column>|<model>\.(create|update|upsert)' -n |
谁写这张表/这个字段 |
| 4 | 双 Prisma schema | rg '<field>' prisma/schema.prisma prisma/schema.mysql.prisma -n |
SQLite + MySQL 两份 schema 是否都要改（不许省） |
| 5 | daemon-SDK 镜像 | rg '<name>' sdk/prismer-cloud/runtime/src -n |
cloud 侧改了，daemon/SDK 侧有没有对称的一份要跟着改 |
| 6 | skill / role 引用 | rg '<name>' sdk/prismer-cloud/built-in-skills sdk/apc/skills -n |
SKILL.md / role template / prompt 里有没有引用它 |
Procedure
1. 锚定改动点
明确改动点的精确标识（符号名 / endpoint 路径 / 列名）。一个改动可能有多个改动点——逐个搜，别只搜一个。
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.
- 17d ago First seen · 169 lines · 60 tokens per session scan A 3f15015970d7
impact-trace is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 3,073 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-09-29.
Other skills, from other repositories
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
debugging-livekit-agents
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Use when the user says "test my agent", "try my agent", "does this work", "why did it call that tool", "it says the wrong thing when I ask X", "test this change", or whenever you have edited an agent and need to check how it…
starlark-dev
Develop and debug Kurtosis Starlark packages. Create packages from scratch, understand the plan-based execution model, use print() debugging, handle future references, and test packages locally. Use when writing or troubleshooting .star files.
oma-debug
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
cli-local-build
Build and test the Kurtosis CLI from source. Compile the CLI binary locally, run it against Docker or Kubernetes engines, and iterate on CLI changes without creating a release. Use when developing or debugging CLI commands.
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…