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 git-opsgit 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/git-ops)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/git-ops"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/git-ops/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/git-ops"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/git-ops.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.00062 | $0.03508 |
| Opus 5.5 | $0.00025 | $0.01403 |
| Sonnet 5.5 | $0.00012 | $0.00702 |
| Haiku 4.5 | $0.00006 | $0.00351 |
Grade A, and why
git-ops 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-ops
收口一个本地 coding task 的 git 动作——在 workdir 上 commit / branch / merge / push，并把 branch+sha 落回 task metadata（apc/05 §1 A2 · S8）。核心纪律：merge 冲突绝不自动解决——停手、列出冲突文件、escalate 给人，workdir 保持现场不回滚（apc/00 §3 不变量 6）。
什么时候用：一个 coding task 改完，需要把改动收口成 commit / 分支、merge 回主线、并把 provenance（branch/sha）记到 task 上。
承重约束（先记死）
commit不自动 stage：cloud git commit只提交已 staged 的内容。你必须先自己git add <task-owned files>，只 stage 本 task 拥有的文件，别把无关改动带进去。- 单任务串行不变量：同一 repo 同时只有一个 coding task 在飞。别假设并发安全。
- prod tag 禁止：四个 prod 触发前缀（
k8s-prod-*/desktop-prod-*/prod-*/ali-k8s-prod-*）的 tag push 被 daemon 拒（真闸是 GitLab protected tags）。 - push 只到 bare 替身：remote 必须是 daemon allowlist 里的纯名字（默认
origin，本地指向 bare 替身）；URL / 带--的值一律被拒。无--force。 - provenance 写 metadata 要用
--set-string：sha / branch 是字符串，用--set（推断 JSON）会把全数字 sha 变成 number（40 位 sha 会被1.2e+39精度毁掉，7 位全数字 sha ≈3.7% 概率）。
工具契约（签名以此为准，先核后用）
cloud git 的 cwd 永远不由你传——它从 --workdir <id> 指向的 IMWorkdir 行读，daemon 侧再 jail 一次。--workspace / --daemon 默认取 dispatch env（PRISMER_WORKSPACE_ID / PRISMER_DAEMON_ID）。
| 命令 | 作用 | 关键 flag |
|---|---|---|
cloud git workdirs |
列 workspace 里的 repo workdir（拿 <workdirId>） |
--workspace --json |
cloud git commit <workdirId> -m <msg> |
提交已 staged 的改动 | -m/--message（必填） |
cloud git branch <workdirId> --name <b> |
建并切到新分支 | --name（必填） |
cloud git merge <workdirId> --source <ref> |
把 <ref> merge 进当前分支（冲突→escalate，绝不自动解决） |
--source（必填） |
cloud git push <workdirId> --branch <b> | --tag <t> |
push HEAD 到分支，或 push tag（prod tag 被拒） | --branch 或 --tag（二选一）· --remote（allowlist 纯名字，默认 origin） |
cloud task meta set <task-id> --set-string k=v |
把 provenance 写进 task metadata | --set-string（值恒字符串） |
- 退出码：成功
0；失败非零。--json下 stdout 是结构化{ok, op, sha?, ref?, cwd, ...}（成功）或{ok:false, op, code, message, files}（失败）。 code:'conflict'是冲突信号，files[]是未合并文件清单——这是承重的 escalation payload。- 权限：
cloud task meta set走 metadata gate = creator / orchestrator / admin / owner，assignee 不在内。写 provenance 这一步必须以主 agent（orchestrator/creator）身份跑——coding agent 自写会被 403。
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 · 190 lines · 62 tokens per session scan A 58a45af718f9
git-ops is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 3,508 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…
commit-pr
Create a git commit and open a pull request (creates a new branch first if on main/master).
git-authoring
Authors and executes git work end to end — Conventional Commits messages, pull-request content, release notes, and pull-request review, plus the repository operations an engineer runs daily: branching, rebasing, squashing, cherry-picking, reverting, merge-conflict resolution, stashes, tags, remotes, and recovery…
changelog-generator
Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes.
handoff
Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.
code-commit
Commit code changes with well-structured messages following Conventional Commits. Use when ready to commit after implementation or bug fix.