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 test-runnergit 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/test-runner)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/test-runner"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/test-runner/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/test-runner"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/test-runner.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.00059 | $0.02959 |
| Opus 5.5 | $0.00024 | $0.01184 |
| Sonnet 5.5 | $0.00012 | $0.00592 |
| Haiku 4.5 | $0.00006 | $0.00296 |
Grade A, and why
test-runner 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-runner
对一个改动选层跑测试并把**新增红（vs baseline）**报回 task 的验收 criterion（apc/02 §2 R1 · apc/05 A1 S7）。核心纪律：环境红（env_blocked）与被测代码红（SUT red）分域——机器坏了绝不判代码红。
什么时候用：一个 coding task 改完进 review，需要按改动面选层跑回归、把结果作为 acceptance criterion 的 pass/fail 证据。
工具契约（签名以此为准，先核后用）
| 命令 | 作用 | 退出码 |
|---|---|---|
apc env doctor |
环境体检（见 env-doctor skill） | 0 全绿 · 78 env_blocked |
apc test [--tier=T0,T1] [--diff] [--json] [--list] |
全层测试编排（包装 scripts/test203/run.ts） |
0 绿 · 1 SUT 红/回归 · 2 用法错 · 78 env_blocked |
cloud task verify-criterion <task-id> <criterion-id> --outcome <passed|failed|n/a|waived> |
把一个 criterion 的判定报回 task | 0 成功 |
apc test的退出码原样透传，含78。把 78 折成 1 会让下游去重试一个根本没跑的圈次——绝不这么干。--json下 stdout 是结构化test203.run/v1产物，含每层TierResult（命令 / 退出码 / failed names / envStatus）+ baseline diff。从 stdout JSON 取结果，人读报告在 stderr。
选层规则（按改动面）
| 改动面 | tier |
|---|---|
src/lib/**（纯库 / 单元） |
T0 |
src/im/**、endpoint / IM 域 |
T1 |
src/app/** 组件 |
T2 |
| e2e / 跨端（需 cloud:3000） | T3 |
跨 src/lib + endpoint 的改动 → --tier=T0,T1。宁可多选一层，不可漏层。
Procedure
1. 先体检（env doctor，取上下文——不是是否跑的最终判据）
apc env doctor > /tmp/apc-doctor.json; DOC=$?
echo "doctor exit=$DOC"
apc env doctor 是全局体检：它 exit 78 只表示"存在某个环境红"，不等于你要跑的 tier 被挡。跑不跑的权威判据是 apc test 自己的退出码——run.ts 按 tier 做逐层 env 门（TIER_ENV_REQUIRES）：
| tier | 需要的环境 |
|---|---|
T0 / T1 / T2 / TD / TA |
无（纯逻辑，不被任何 infra 红挡） |
T3 |
cloud（:3000） |
T4 |
mysql + redis + cloud |
所以：doctor 红在你选的 tier 的 env 需求之外（典型 toolchain.node pin 漂移之于 T0/T1）→ 记一条故障域备注即可，照跑。别把全局 78 当作"停"——那会因为一条无关的 toolchain 红漏掉整轮回归。真正的 env_blocked 由第 2 步 apc test 的 exit 78 表达（run.ts 只在你选的 tier 的 infra 缺失时才给 78）。
2. 选层跑（apc test）
按上表选层。跨 src/lib + endpoint 的改动：
apc test --tier=T0,T1 --diff --json > /tmp/apc-test.json; T=$?
echo "apc test exit=$T"
3. 解析 TierResult + 判据
从 /tmp/apc-test.json 读结构化产物，真实 schema（字段名以此为准）：
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 · 170 lines · 59 tokens per session scan A 2c791fa36d78
test-runner is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 2,959 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
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
qa/test-strategy
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.
Codeception Testing
Expert-level Codeception testing skill for PHP applications. Covers acceptance, functional, and unit testing with the Actor pattern, BDD-style syntax, Page Objects, API testing, and database helpers.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.