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 releasing-prodgit 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/releasing-prod)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/releasing-prod"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/releasing-prod/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/releasing-prod"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/releasing-prod.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.00074 | $0.00810 |
| Opus 5.5 | $0.00030 | $0.00324 |
| Sonnet 5.5 | $0.00015 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
releasing-prod 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.
What it actually says
发生产（releasing-prod）
铁律
main 是生产的唯一通道；prod 内容必须先在 test 同版本验证通过。
ali-k8s-prod-* tag 只打 main merge 后的 commit。prod deploy job 是 manual——手动那一下就是 owner 审批点，代点前必须有 owner 原话授权。
门槛顺序（逐步过，任何一步红则停）
- test 前置：同内容已在 test 验证（发版记录 / 管线号 / 冒烟结果可查）。无记录不发。
- owner 授权：发 prod 的原话指令在案。
- 本地门：干净树 +
npm run check0 errors。 - 版本：
cat /VERSION；prod tag 版本 = 发 test 的版本或其后；禁止四段版本制造镜像漂移。 - merge：develop → main MR（描述含 test 验证证据），merge。
- 迁移：受保护 tag
prod-schema-migrate-YYYYMMDD-vX.Y.Z管线：prod_incremental_schema_preflight（产出唯一planSha256）→ manualprod_incremental_schema_apply（resource_group: prod-schema 串行）。先迁后发；任何本地机器不碰 prod 库。 - 发版：tag
ali-k8s-prod-YYYYMMDD-vX.Y.Z→ build_job_prod →ali_k8s_deploy_prod（manual，授权后点）。 - 节流 + 留证 + 冒烟：只留目标链；prod 双域（prismer.cloud / prod.docbrew.cn）冒烟；回滚预案（镜像 digest 回退路径）先写进汇报再动手。
禁区
- prod tag 指向非 main commit（feature/develop 直发）
- 未经 owner 授权点 manual deploy / manual apply
- prod 库任何本地直连
- 迁移未过 preflight 直接 apply
合理化反驳表
| 借口 | 现实 |
|---|---|
| 「test 都绿了，prod 肯定行」 | prod 变更门是授权门不是技术门；跳过授权=不可回退事故。 |
| 「先发了再看着办」 | prod 没有「看着办」；回滚预案是发版的一部分，不是事后补的。 |
| 「迁移很小，直接上」 | prod 迁移走 planSha256 受控管线；「小」不是绕过 preflight 的理由。 |
| 「owner 大概会同意」 | 「大概」不是授权。停下来问。 |
红旗（出现即停）
- 无 test 验证记录
- 无 owner 原话授权
- 没写回滚预案就想点 manual
- tag 与 main commit 不符
归宿
源头 = sdk/apc/skills/releasing-prod/SKILL.md（2026-09-07 归入 apc，随仓库版本控制）；.claude/skills/ 为 agent 运行时安装副本，改源头后同步复制。
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 · 50 lines · 74 tokens per session scan A 405e0e5ea1a9
releasing-prod is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 810 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
npm-trusted-publishing
Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration.
oma-dev-workflow
Configure development tasks, git hooks, CI/CD, or release automation. Use when creating or fixing a repository development workflow.
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
ci-cd-pipelines
When designing GitHub Actions workflows, optimizing pipeline speed, implementing deployment gates.
production-release-gating
Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel…
data-platform-ci-cd-and-release-management
Guides agents through CI/CD and release management for data platforms. Use when promoting pipeline code, SQL models, contracts, infra, or configuration across environments with validation gates, staged rollout, and rollback awareness.