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 prismer-obsidiangit 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/prismer-obsidian)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/prismer-obsidian"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/prismer-obsidian/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/prismer-obsidian"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/prismer-obsidian.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.00022 | $0.00994 |
| Opus 5.5 | $0.00009 | $0.00398 |
| Sonnet 5.5 | $0.00004 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
prismer-obsidian 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Vault
Use this skill for filesystem-first Obsidian vault work: reading notes, listing notes, searching note files, creating notes, appending content, and adding wikilinks.
Vault path
Use a known or resolved vault path before calling file tools.
Require an explicitly configured OBSIDIAN_VAULT_PATH or a vault path supplied by the user. If absent, report missing configuration; do not create or write to a fallback vault.
File tools do not expand shell variables. Do not pass paths containing $OBSIDIAN_VAULT_PATH to read_file, write_file, patch, or search_files; resolve the vault path first and pass a concrete absolute path. Vault paths may contain spaces, which is another reason to prefer file tools over shell commands.
If the vault path is unknown, terminal is acceptable for resolving OBSIDIAN_VAULT_PATH or validating the user-supplied path. Once the path is known, switch back to file tools.
Read a note
Use read_file with the resolved absolute path to the note. Prefer this over cat because it provides line numbers and pagination.
List notes
Use search_files with target: "files" and the resolved vault path. Prefer this over find or ls.
- To list all markdown notes, use
pattern: "*.md"under the vault path. - To list a subfolder, search under that subfolder's absolute path.
Search
Use search_files for both filename and content searches. Prefer this over grep, find, or ls.
- For filenames, use
search_fileswithtarget: "files"and a filenamepattern. - For note contents, use
search_fileswithtarget: "content", the content regex aspattern, andfile_glob: "*.md"when you want to restrict matches to markdown notes.
Create a note
Use scripts/write_note.py with an explicitly authorized vault, relative Markdown path, expected revision and content on stdin. This applies the path, lock, revision and atomic-write checks; do not bypass them with direct writes.
Append to a note
Prefer a native file-tool workflow when it is not awkward:
What ships with it
5 files 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 · 81 lines · 22 tokens per session scan A 72a74d80e304
prismer-obsidian is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 994 once invoked, about $0.0001 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.
memex-best-practices
Zettelkasten best practices for building a high-quality knowledge graph.
memex-organize
Periodic maintenance of the Zettelkasten card network.
memex-recall
Load prior knowledge from Zettelkasten memory when the task likely benefits from past context.
memex-sync
Sync Zettelkasten cards across devices via git.