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 weekly-reviewgit 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/weekly-review)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/weekly-review"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/weekly-review/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/weekly-review"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/weekly-review.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.00027 | $0.00536 |
| Opus 5.5 | $0.00011 | $0.00214 |
| Sonnet 5.5 | $0.00005 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
weekly-review 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Review
Resolve review period and timezone from the request/context. Use tasks, memory, and okr only where available and authorized. External calendars and inboxes are optional sources, never assumed capabilities.
- Read completed and active tasks, relevant decisions, goals and waiting items.
- Record outcomes, owner, deadline, blocker, last activity and source link. Silence is not evidence of completion.
- Identify overdue work, missing next actions, duplicates and conflicting states.
- Review next week's capacity only from available calendar/user evidence. Without it, state that capacity is unverified instead of inventing free hours.
- Propose a small set of outcomes ranked by deadline, consequence and dependency. Name deferred work and evidence gaps.
- Apply updates already authorized by the user, then read back changed records. Draft follow-up messages unless sending them was requested.
- Report wins, risks, waiting items, next-week outcomes, verified updates and gaps.
Do not create cron jobs or a recurring monitor merely because this skill ran. Scheduling is a separate explicit request handled through platform scheduling.
Coverage and planning detail
Declare the authoritative system when stores disagree. Inspect both the completed
week and the next 1-2 weeks for travel, preparation, deadlines and commitments.
Classify each capture item as next action, project, waiting, scheduled, someday,
reference, archive proposal or delete proposal; count unprocessed items. Consult
prismer-email-inbox-triage for thread-level email handling only when authorized.
For every waiting item identify who owes what, its supporting record/event/thread and a proposed review or follow-up date. Keep proposed dates separate from agreed deadlines. For every active project identify an outcome and next action or mark it paused/unresolved. Rank outcomes by consequence, deadline, dependency and effort; reserve slack rather than allocating all apparent free hours. Explicitly name deferred work. Return wins, overdue/at-risk work, waiting items, stalled projects, next-week outcomes/calendar constraints, proposed updates and coverage gaps.
What ships with it
2 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 · 50 lines · 27 tokens per session scan A 436f38ecd328
weekly-review is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 536 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
switch-clients
Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.
meeting-transcript
Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering.
atlassian-jira-sync
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.
things
Manage Things 3 on macOS: add/update todos and projects via URL scheme, read inbox/today/upcoming, search tasks. Syncs to iOS.
cast-pass
Hand this session to a teammate so it lands in their inbox with everything they need. Pins where the work stands and what is next, adds them as an owner, and sends them the brief. Use when work should continue under someone else, when a decision is theirs, or when asked to pass, hand over, or assign a session.
outlook-calendar
A skill for managing Microsoft Outlook and Microsoft 365 calendar events through a connected account.