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 webapp-qagit 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/webapp-qa)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/webapp-qa"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/webapp-qa/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/webapp-qa"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/webapp-qa.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.00029 | $0.00432 |
| Opus 5.5 | $0.00012 | $0.00173 |
| Sonnet 5.5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
webapp-qa 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.
What it actually says
Web Application QA
For the full five-phase exploratory method, read references/dogfood/GUIDE.md; its taxonomy and report-template links resolve within this bundle.
Use the user-supplied target URL, scope and existing test accounts. Inspect the available browser tools or Playwright setup first; never invent browser tool names. Without a working browser, report the blocker and limit claims to checks actually performed.
- Map the main user journeys, navigation, forms and error/empty states.
- Exercise each journey with positive and negative inputs. Inspect console and network failures after navigation and significant interactions.
- Inspect screenshots at desktop and mobile sizes for clipping, overlap, loading failures and keyboard accessibility.
- Reproduce each suspected defect. Record URL, exact steps, expected/actual behavior, console evidence and screenshot file. Separate application bugs from unavailable dependencies or test-environment failures.
- Deduplicate, prioritize by user impact, and use references/issue-taxonomy.md plus templates/dogfood-report-template.md as report structure.
- State tested, untested and blocked areas. Passing HTTP status alone is not a passing user journey. Never fill missing evidence with plausible descriptions.
- Attach the report and requested evidence as task-bound assets using the actual platform delivery contract. Do not invent flags or use MEDIA markers.
Use a task-owned local fixture for browser-tool smoke tests before touching a live account. Record desktop/mobile viewport, keyboard, console, clipping and positive/negative form results independently; a fixture does not certify the user's real application.
Keep test mutations within the user's authorized scope. Do not submit real payments or send external messages as incidental QA actions.
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 · 42 lines · 29 tokens per session scan A 2a66311a5023
webapp-qa is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,386 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 432 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
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
flutter-skill
Automate and test Flutter applications — launch apps, inspect widgets, tap elements, enter text, scroll, swipe, take screenshots, validate state, and debug via Dart VM Service Protocol. Use when the user wants to run Flutter app tests, automate Flutter UI interactions, inspect widget trees, debug a running Flutter…
lov-runtime-verification
Verify client runtime fixes on actual desktop builds, physical iOS/Android devices, React Native/Flutter hosts, and deployed Web/PWA browsers with comparable workloads and lifecycle checks.
running-bug-review-board
Runs real-user QA, manual test plans, UX bug hunts, build sign-off, bug filing, and bug triage for web or iOS/iPadOS apps. Use when asked "QA this", "is this ready to ship?", or similar. Produces P0/P1/P2 bug reports, YES/NO phase sign-off, tracker sync guidance, and an HTML QA dashboard; keeps Interactive BRB triage…