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
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/office-artifacts)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/office-artifacts"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/office-artifacts.svg" alt="Measured on agentmods" 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.00075 | $0.02309 |
| Opus 5 | $0.00037 | $0.01154 |
| Sonnet 5 | $0.00015 | $0.00462 |
| Haiku 4.5 | $0.00007 | $0.00231 |
Grade A, and why
office-artifacts 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 8d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Office Artifacts
Produce real binary office files (not markdown-as-PDF) by writing each
one into the artifacts dir ($PRISMER_ARTIFACTS_DIR /
<artifacts_dir> from <execution_context>). Prose-only completions are
not valid.
Delivery contract — explicit, two steps (release202/09 P2)
Delivery is explicit. Writing a file into the artifacts dir does NOT
deliver it — there is no auto-scan. You must run cloud deliver for
every file you want the user to receive.
-
Write each deliverable (PDF / DOCX / PPTX / XLSX / CSV / image / archive) into the artifacts dir. Drafts / intermediate scratch →
$PRISMER_SCRATCH_DIR(never delivered). -
Deliver it with the absolute path:
cloud deliver "<artifacts_dir>/report.pdf"This attaches the file to your current reply (动作 A — it rides the same message as your text summary). Run it once per file. The command prints the
assetIdon success.
-
$PRISMER_ARTIFACTS_DIRis injected as an env var by spawn-style adapters (claude-code / codex / openclaw). Hermes does not inject the env var — read the absoluteartifacts/path from the dispatch prompt's[Artifacts directive]block and write there. Either way, pass the absolute path tocloud deliver. -
Hermes also has NO per-dispatch env ids (
PRISMER_RUN_ID/PRISMER_TASK_ID/PRISMER_CONVERSATION_IDare all unset), so plaincloud deliver <path>cannot find the dispatch and exits with an error. On hermes you MUST copy<run_id>(or<task_id>) and<conversation_id>from<execution_context>and pass them as flags:# Hermes — ids come from <execution_context>, not env: cloud deliver "<artifacts_dir>/report.pdf" --run-id "<run_id>" --conversation-id "<conversation_id>"Spawn-adapter agents (claude-code / codex) do not need these flags — their env is already set; plain
cloud deliver "<abs-path>"works there. -
Sending a file as its OWN message (动作 B — separate from your reply, e.g. to drop it into the session standalone): use
cloud file send "$PRISMER_CONVERSATION_ID" "<abs-path>". On hermes the conversation id comes from<execution_context><conversation_id>(pass it as the positional), and you must also add--run-id "<run_id>"so the proxy activates. Prefercloud deliver(动作 A) for the normal "here is the document you asked for" case. -
Attaching a file to a message you ALREADY sent (动作 A2 — "I already replied, now I produced a file I want on THAT message"):
cloud send/cloud file sendreturn amessageId; runcloud attach <messageId> "<abs-path>"to append the file to that existing message (it does NOT start a new one). On hermes also pass--run-id "<run_id>"and--conversation-id "<conversation_id>"(both copied from<execution_context>). Use this only when the reply already exists; for "this reply carries the file" usecloud deliver(动作 A). -
Do NOT run
cloud task completeto deliver a chat reply — the platform closes the turn from your final reply (dispatch-reply path). -
cloud task attach/cloud task completeare OPTIONAL and ONLY for when you are genuinely working a kanban TASK you were assigned (e.g. moving a board card toreview/done). For a normal @-mention chat reply, never touch them —cloud deliveris all you need. -
Rejections are visible: if
cloud deliverprints a non-zero exit / error (bad MIME, renamed extension, file not found), the file was NOT delivered — fix it and re-run. Do not claim a file you failed to deliver.
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.
- 8d ago First seen · 199 lines · 75 tokens per session scan A 38997d0ff03f
office-artifacts is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,410 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 2,309 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
work-markitdown
A document conversion tool that turns files such as Word documents, PDFs, PowerPoint presentations, spreadsheets, images, HTML, and CSV files into Markdown. Markdown is plain text with simple symbols for headings, lists, and other structure.
markitdown
A local document-conversion guide built around MarkItDown, a tool that turns files such as DOCX, PDF, PPTX, XLSX, images, HTML, and CSV into Markdown text.
markitdown
Convert files, URLs, and documents to Markdown using the markitdown MCP server. Activate when the user asks to convert, extract, or read content from PDFs, Word docs, PowerPoints, spreadsheets, images, audio files, or any URL.
vision-augment
A visual and document-analysis service for agents that cannot directly understand images. It can inspect pictures, read text with OCR, and parse documents such as PDF, Word, PowerPoint, spreadsheet, and HTML files.
extract-nda-and-generate-checklist
Extract key terms from a non-disclosure agreement, then generate a compliance checklist spreadsheet tracking obligations and deadlines.
extract-receipts-to-expense-report
Extract merchant, date, amount, and category from receipt photos and PDFs in one call, then generate an XLSX expense report with a totals row.