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-githubgit 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-github)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/prismer-github"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/prismer-github/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-github"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/prismer-github.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.00793 |
| Opus 5.5 | $0.00009 | $0.00317 |
| Sonnet 5.5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
prismer-github 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prismer execution contract
This is the uniquely named prismer-github skill, adapted from Hermes.
Use the actual tools exposed by the executing host; examples using terminal,
process, delegate_task, vision_analyze or browser_* are not tool registrations.
Missing dependencies do not hide this skill. Report command startup, version,
account/permissions and task-specific live verification separately. Use task-owned
artifact paths and existing user authorization; do not change shared accounts,
Runtime/provider configuration, global security settings or unrelated work.
See NOTICE.md and LICENSE for resource provenance. Runtime availability and
upstream-entry suppression are owned by the integration layer.
GitHub
Work GitHub end to end with the gh CLI (REST fallback where noted): auth,
issues, the PR lifecycle, issue-to-PR delivery, code review, and repo
management. This skill consolidates six former skills; each workflow lives
complete in its reference file — ALWAYS read the matching reference before
starting that workflow, the body below only routes.
Routing
| Task | Read first |
|---|---|
| Auth broken / new machine / token or SSH setup / gh login | references/auth.md |
| Create, triage, label, assign, close issues | references/issues.md |
| Branch, commit, open PR, watch CI, merge | references/pr-workflow.md |
| Carry an ISSUE to a verified PR (full delivery loop) | references/issue-to-pr.md |
| Review someone's PR: diffs, inline comments, verdict | references/code-review.md |
| Clone/create/fork repos, remotes, releases | references/repo-management.md |
Supporting assets: scripts/gh-env.sh + scripts/git-credential-token.py
(auth helpers), templates/ (PR bodies, bug report, feature request),
references/ci-troubleshooting.md, references/conventional-commits.md,
references/github-api-cheatsheet.md, references/review-output-template.md.
Core discipline (applies to every workflow)
- Before use, resolve SKILL_ROOT to this installed directory and run
python3 "$SKILL_ROOT/scripts/ensure-gh.py". Missing gh is automatically installed within existing host permissions, then version and auth are checked separately. Readreferences/auth.mdfor account and target repository permission gates. - Prefer
ghover raw REST; drop togh apionly for endpoints the porcelain lacks (the cheatsheet lists them). - Never report CI green without checking
gh pr checksyourself; never claim merged without verifyingstate,mergedAt. - Read full context before writing:
gh issue view --comments/gh pr view --comments— decisions live in threads, not titles. - Sweep for duplicates before creating anything:
gh pr list --search/gh issue list --search.
What ships with it
21 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.
- LICENSE 1.0 KB
- NOTICE.md 948 B
- references/auth.md 5.0 KB
- references/ci-troubleshooting.md 5.6 KB
- references/code-review.md 14 KB
- references/conventional-commits.md 3.1 KB
- references/github-api-cheatsheet.md 7.0 KB
- references/issue-to-pr.md 6.2 KB
- references/issues.md 9.1 KB
- references/pr-workflow.md 10 KB
- references/repo-management.md 14 KB
- references/review-output-template.md 3.1 KB
- scripts/ensure-gh.py 5.8 KB runs code
- scripts/gh-env.sh 1.1 KB runs code
- scripts/git-credential-token.py 1.8 KB runs code
- scripts/github-api.py 2.7 KB runs code
- scripts/github-context.py 1.1 KB runs code
- templates/bug-report.md 469 B
- templates/feature-request.md 598 B
- templates/pr-body-bugfix.md 513 B
- templates/pr-body-feature.md 580 B
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 · 75 lines · 22 tokens per session scan A 8eddaa70a4cb
prismer-github 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 793 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
pr-review
Review a GitHub pull request: analyzes changed files to select relevant reviewers, loads project and user memory, runs reviewers in parallel, lets the user pick which findings to post, then submits the review on behalf of the user via gh CLI.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".