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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Prismer-AI/PrismerCloudnpx agentmods add skills/prismer-ai/prismercloud/bug-reproduceWrote 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/bug-reproduce)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/bug-reproduce"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/bug-reproduce/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/bug-reproduce"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/bug-reproduce.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.00061 | $0.03595 |
| Opus 5.5 | $0.00024 | $0.01438 |
| Sonnet 5.5 | $0.00012 | $0.00719 |
| Haiku 4.5 | $0.00006 | $0.00360 |
Grade C, and why
bug-reproduce scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
d=.e2e-tmp/apc/bug-reproduce && rm -rf "$d" && mkdir -p "$d" # repo-relative，已在 .gitignore Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **agent-runnable** | 你能无人值守跑；一条命令（脚本/测试/curl）能贴出调用 + 输出。 | How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bug-reproduce
把一个已知 bug 变成紧、可变红的复现器（失败测试 / 脚本），然后用反转负控证明这个复现器真的锁住了那个 bug——不是恰好绿着（apc/05 §2 S1 · apc/12 bug-reproduce 行；纪律移植自 built-in diagnosing-bugs 的 Phase 1 复现 loop）。
什么时候用：一个 bugfix task 开工的第一步——在读代码建假设之前。diagnosing-bugs 的铁律：没有一个能对这个 bug 变红的信号，再多盯代码也没用。本 skill 只补 diagnosing-bugs 缺的那一环：负控——把 fix 撤掉/把 bug 注入回去，复现器必须变红。
铁律：一个复现器只有走完 RED → GREEN → 反转 RED 才算数。只到 GREEN 不算——一个无论 bug 在不在都绿的"复现器"是开卷考试，不是复现（apc/12 §0 负控纪律）。
复现器四判据（照 diagnosing-bugs Phase 1 完成标准）
一个复现器必须是：
| 判据 | 含义 |
|---|---|
| red-capable | 它驱动真正的 bug 代码路径、断言用户描述的确切症状——能对这个 bug 变红，修好后变绿。不是"没崩就算过"。 |
| deterministic | 同一输入每次同一结论（非确定 bug：钉时间/种 RNG/隔离 FS，把复现率拉到可调试）。 |
| fast | 秒级不是分钟级。 |
| agent-runnable | 你能无人值守跑；一条命令（脚本/测试/curl）能贴出调用 + 输出。 |
Procedure
1. 钉环境 + 建复现器（RED）
在一个干净的、确定性的 workspace 里写出最小失败测试/脚本，然后跑它，看它变红：
d=.e2e-tmp/apc/bug-reproduce && rm -rf "$d" && mkdir -p "$d" # repo-relative，已在 .gitignore
# …在 "$d" 里写 subject + repro…
node "$d"/repro.mjs; echo "exit=$?" # 或 apc test --tier=<T> --json / pytest / go test …
隔离场景的临时目录用 repo-relative 的 .e2e-tmp/…，不要用 mktemp -d：复现器本身就是证据，判据在你跑完之后把你引用的 path:line 读回磁盘——/tmp 从仓库根不可解析、收尾 rm -rf 更是把唯一产物销毁（test204「证据销毁反 pattern」的同一个坑）。本地真仓库里的 bug 则直接在真路径上做。
- 复现器必须断言用户描述的症状本身（
clamp(-5,0,10)应得 0 而非 -5），不是"没抛异常"。 - 记下确切症状：断言消息、错误、非零退出码。这就是 RED。
- 真仓库里的 bug：复现命令可以是选层的
apc test --tier=<T> --json（读exitCode：0绿 ·1SUT 红 ·78env_blocked）。env_blocked 不是复现——是环境红，先apc env doctor。
2. 最小 fix（GREEN）
打最小修复（只改让复现器变绿所需的那一点），重跑复现器，看它变绿（exit=0）。不顺手清理别的——本步只证明"这个 fix 让这个复现器绿"。
3. 反转负控（承重——RED again）
这是本 skill 的命根子。 把 fix 撤掉——把 bug 注入回去，重跑同一条复现器命令：
# 首选：直接编辑源文件，把 buggy 的那一行 body 原样写回去
node "$d"/repro.mjs; echo "exit=$?" # 必须再次 RED（非零退出 / AssertionError）
反转手法只有一个首选：直接编辑源文件把 bug 写回去。
⚠️
git stash/git checkout在共享工作树里是有害指令，默认不许用。 本仓库常态是多个并发 session 共用一个 working tree、几百个未提交改动同时在飞——git stash会把别人正在做的改动一起卷走，git checkout <file>会丢掉别人对同一文件的未提交编辑。这类操作不可逆地毁坏他人工作，代价远大于它省下的那一次手工编辑。只有在你独占这个 working tree（自己的 worktree / 一次性容器）且已确认
git status干净时，git stash才是等价手法；否则一律手工反转。反转的语义（把 bug 放回去）才是承重的，用什么手法不是。
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 · 151 lines · 61 tokens per session scan C 0556353c59db
bug-reproduce is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 3,595 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). 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…