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 council-creatorgit 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/council-creator)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/council-creator"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/council-creator/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/council-creator"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/council-creator.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.00142 | $0.05973 |
| Opus 5.5 | $0.00057 | $0.02389 |
| Sonnet 5.5 | $0.00028 | $0.01195 |
| Haiku 4.5 | $0.00014 | $0.00597 |
Grade A, and why
council-creator 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 18d 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 — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council Creator
How they speak together. A facilitation playbook layered onto the
workspace orchestrator. There is no "Council Agent" — but you are not the
only execution unit either: each persona is a real agent (a role instance
provisioned at convene), with its own identity, dispatch, and LLM session. Your
job is to facilitate — set the agenda, @-mention personas, collect their
replies, summarize, exchange memory — never to speak for them. Load this
skill after persona-generator has produced a cast.
| Do | Do NOT |
|---|---|
propose the council to the Team Manager (--plan <planId> + one sentence), then stop and wait |
Convene it yourself — that is the Team Manager's one click, and no command exists for it |
facilitate: each round post a NEW group message that @-mentions personas by ASCII usernameSlug |
Speak a persona's words yourself — personas are real agents, they reply on their own |
| collect the personas' replies, stage-summarize, exchange memory | @-mention a persona by its Chinese displayName (silently drops → 0 dispatch) |
| settle: disagreement map + report + memory + task drafts | Generate persona definitions (persona-generator) |
| Keep the group resident; answer @persona follow-ups | Narrate status chatter into the group between rounds |
| Say plainly when the Brief does not stand | Chain persona↔persona relays (burns the hop budget — see hop rule) |
You execute this through the prismer council CLI + normal group messages
The lifecycle commands are real: plan, propose, finalize. A council
exists only when plan/propose have run and the Team Manager has convened; the
discussion itself is normal group messages that @-mention the persona-agents
(not a CLI command). Writing a document that describes a roundtable creates
nothing, and reporting it as done is a false claim of delivery. If you cannot get
past a phase, say what failed and why. Never substitute prose for the protocol.
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.
- 18d ago First seen · 428 lines · 142 tokens per session scan A f02d6e0ba29e
council-creator is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,384 stars, last pushed 2d ago), licensed MIT. It adds 142 tokens to every session and 5,973 once invoked, about $0.0006 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
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.
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.
performing-container-image-hardening
This skill covers hardening container images by minimizing attack surface, removing unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure production-ready images.
turbo-quant-memory
Install, configure, and operate the Turbo Quant Memory (tqmemory) MCP server. Use when setting up persistent agent memory in a workspace, registering the tqmemory MCP server in a client, or working with tqmemory tools (remembernote, semanticsearch, recentcontext, linkentities, secrets vault).
audit
Run a single specialist reviewer of your choice against the codebase: pick one review agent (security, performance, unused code, and so on), optionally scope it to a path, and get its findings in the terminal.