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 claim-agent-ownershipgit 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/claim-agent-ownership)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/claim-agent-ownership"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/claim-agent-ownership/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/claim-agent-ownership"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/claim-agent-ownership.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 62 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 199 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00101 | $0.02915 |
| Opus 5 | $0.00051 | $0.01458 |
| Sonnet 5 | $0.00020 | $0.00583 |
| Haiku 4.5 | $0.00010 | $0.00292 |
Grade A, and why
claim-agent-ownership scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
the cloud HTTP endpoint directly via `curl` (or the equivalent fetch from the How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claim Agent Ownership
When two daemons (typically Mac Studio at home + a k8s pod) both run agent.host.declare
for the same agent, the first one wins ownership and the second registers a
contested binding. The user UI surfaces a "binding contested" badge and the cloud's
resolveAgentDaemonRoute keeps routing dispatches to the original owner — but a
human-driven or orchestrator-driven decision is needed to converge.
This skill is the orchestrator's tool for that decision. It calls the server's authoritative rebind endpoint, which atomically:
- flips
im_agent_bindings.boundDaemonIdto the chosen target daemon - writes an audit row with
boundBy='user-explicit'(or'orchestrator') - returns the in-flight task count on the previous owner so the orchestrator can wait / drain before redirecting traffic
- emits a sync event (
agent.binding.rebound) so other daemons drop their hosting state for the agent
When to use
- A sync event with type
agent.binding.contestedarrives in your inbox. - A user explicitly asks "the agent is bouncing between machines — pin it to my laptop".
- You (orchestrator) decide to migrate an agent off a misbehaving daemon (high error rate, stale heartbeats, etc.) and a target is available.
- Devices panel shows >1 daemon claiming the same agent and the user requests arbitration.
Do not use it for:
- Healthy single-daemon bindings (no contention — nothing to claim).
- Agents the orchestrator does not own / has no permission for (server rejects 403).
- Routing decisions that should be reversible at the chat-message level (use
metadata.daemonIdoverrides in single dispatches instead).
API
There is no generic cloud im get / cloud im post subcommand in the
runtime CLI today (release 201 audit, sdk/prismer-cloud/runtime/src/cli/).
A dedicated cloud agent rebind verb is not landed either. The skill calls
the cloud HTTP endpoint directly via curl (or the equivalent fetch from the
orchestrator's MCP runtime), authenticating with the daemon API key already
present in the environment as $PRISMER_API_KEY:
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.
- 12d ago First seen · 255 lines · 101 tokens per session scan A 5d75c01ab4a7
claim-agent-ownership is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,534 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 2,915 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
recall
Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
agent-prompts-warmup
Audit and sync agent instruction files across all coding agent formats. FRE (first-run) checks scaffolding completeness; ongoing use keeps files in sync after edits.
docmancer
Work from the same local memory as every other coding agent on this machine. Recall prior decisions, preferences, instructions, and project conventions that Claude Code, Codex, Cursor, and other agents wrote here, with cited sources, fully local. Also searches a separate local technical-documentation index.
linksee-memory
The bridge to the agent's "past self". Before any new task, file edit, decision, or right after a failure, recall past caveats (pain records) / learnings (growth log) / implementation history from linksee-memory. This is the only way to solve Claude Code's "memory amnesia every session" problem. The "never repeat the…
setup-bot
Diagnose and fix Telegram bot connection issues -- verify config, test send, resolve common errors.