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 release-taggit 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/release-tag)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/release-tag"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/release-tag/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/release-tag"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/release-tag.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.00046 | $0.04310 |
| Opus 5.5 | $0.00018 | $0.01724 |
| Sonnet 5.5 | $0.00009 | $0.00862 |
| Haiku 4.5 | $0.00005 | $0.00431 |
Grade A, and why
release-tag 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-tag
发版打 tag（apc/01 §2 release-tag，收口步 6）。它把测试→上线的焊点焊死：没有 tier 全绿 / baseline 无新红的结构化证据，审批请求根本不创建、tag 绝不 push。tier 门跑真 run.ts 读真退出码；tag 名按 <channel>-<target>-YYYYMMDD-vX.Y.Z 算；审批通过后 git tag && push 到本地 bare mirror 替身（真 GitLab push + pipeline 轮询 = M5）。
什么时候用：release-preflight 绿 + release-db-config-sync 无阻塞之后，要把一个 test 版本推上 CI。
承重纪律（发版 skill 的命根子，先记死）
- prod 前缀 tag 必拒（不变量 2 · 两人闸）。四个映射
APP_ENV=prod的前缀——k8s-prod-*/desktop-prod-*/prod-*/ali-k8s-prod-*——先于一切 git / tier 动作硬拒，本 verb 不做任何 git 动作。别试 prod：真 prod 红线由 GitLab protected tags（P-1，运维配置）落地，本 skill 只护到"不替你打 prod tag"。要发 prod = 人走 M5 路径。 --tier必须显式传，没有默认值。TD（桌面冒烟）在apps/desktop/e2e/smoke/无 spec 时会自动skipped-with-note（passed:0/failed:0），单独拿它当发版门是一道不可能红的空门——之前 SKILL 范例全不带--tier让 agent 照抄默认值正是这么踩的坑（apc/12§0.12）。选一个会真执行断言的层，例如--tier=T0,T1；prod 前缀路径（下方触发）例外——它先于 tier 门拒绝，不需要--tier。- tier 绿是 push 的硬前置，"绿"必须是真跑过用例。tier 红 /
env_blocked/ 空跑（该轮所有 tier 的passed+failed合计为 0，即一个用例都没真执行）⇒blocked，审批请求不创建、tag 不 push。不许放松 tier、挑能绿的层、或拿一个恰好全 skip 的层骗过门。 - 审批门不可跳。tier 绿但未审批 =
staged（dry-run：出 tag + tier 证据，不 push）。批准路径必须同时传--task <taskId> --approved <approvalId>；CLI 从 cloud 读回批件和 task，校验approved/release_tag/ task 绑定 / 非自批，且两者 metadata 的 commit SHA 必须一致。随机 token 不再能放行。 - tag 打获批 commit，不打 HEAD。并行工作使 HEAD 漂移也不得把未审内容带入 tag；获批 SHA 不在 repo 则 fail-closed。
Anti-pattern（直接判红）
- ❌ 给
--target prod或手拼 prod 前缀 tag 想让 skill 打 prod。命中即 blocked，别绕。 - ❌ tier
blocked时先打 tag 再补测试。焊点就是不让这发生。 - ❌ 拿到
staged就以为发版完成。staged 是"等审批"，tag 还没 push。 - ❌ 用
git tag+ 裸git push origin手工绕过本 verb，跳过 tier 门和审批门。
工具契约（签名以此为准）
apc不在 PATH——在仓库根用npx tsx sdk/apc/bin/apc.ts <sub>。
| 命令 | 作用 | 退出码 |
|---|---|---|
npx tsx sdk/apc/bin/apc.ts release tag [--channel k8s|desktop] [--target test|prod] [--version X.Y.Z] --tier=<tiers> [--task <taskId> --approved <approvalId>] [--json] |
prod 人闸 → tier 门 → cloud 批件/task/commit 他证 → 把获批 SHA push 到本地 bare mirror | 0 green（pushed）· 3 staged（tier 绿待审批）· 1 blocked（tier 红 / 他证失败 / prod 拒 / push 失败）· 2 用法错 |
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 · 195 lines · 46 tokens per session scan A 86d3ff8b4c2c
release-tag is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 4,310 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
create-release
Create a versioned GitHub release with changelog.
ijfw-preflight
Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.
evolve-lite:publish
Publish a private guideline to a configured write-scope repo.