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 dungnotnull/hybrid-harness-chaos-process-prm --skill s12-cloakbrowser-testinggit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s12-cloakbrowser-testing)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s12-cloakbrowser-testing"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s12-cloakbrowser-testing/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/dungnotnull/hybrid-harness-chaos-process-prm/s12-cloakbrowser-testing"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s12-cloakbrowser-testing.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.00143 | $0.03333 |
| Opus 5 | $0.00072 | $0.01666 |
| Sonnet 5 | $0.00029 | $0.00667 |
| Haiku 4.5 | $0.00014 | $0.00333 |
Grade A, and why
cloakbrowser-testing 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 11d 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CloakBrowser Testing (s11)
Purpose
Execute deep, comprehensive test case execution using CloakBrowser as the primary browser automation engine. Establish pre-chaos behavioral baselines, validate post-deployment functionality, and generate test evidence that feeds into resilience scoring and postmortem learning.
Prerequisites
- PRD and user flows from s01 (BA Requirements) or s01-1 (User Flow Writing)
- Pipeline YAML from s04 (Pipeline Design)
- Service deployed and accessible in target environment
- CloakBrowser installed and configured
- Test environment URLs available
Input Contract
| Input | Source | Required |
|---|---|---|
| PRD with acceptance criteria | s01 (workflow_context) | Yes |
| Deployed application URL(s) | s04, s05 (pipeline outputs) | Yes |
| Feature flag states (what's enabled) | s08 output | No |
| Expected steady state behavior | s15 output | No |
| Test framework preference | s02 taste (testing category) | No |
| Previous test results (for regression) | s25 (postmortem feedback) | No |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Test execution report | .commandcode/artifacts/test-report.html |
HTML |
| Test results (JUnit XML) | .commandcode/artifacts/test-results.xml |
XML |
| Coverage report | .commandcode/artifacts/coverage/index.html |
HTML |
| Screenshot evidence | .commandcode/artifacts/screenshots/ |
PNG |
| Accessibility audit report | .commandcode/artifacts/a11y-report.html |
HTML |
| Performance metrics | .commandcode/artifacts/perf-metrics.json |
JSON |
| Pre-chaos baseline data | s18 (game day), s24 (scoring) | JSON |
| Test context | workflow_context.artifacts | YAML object |
Testing Strategy
PRE-DEPLOYMENT POST-DEPLOYMENT PRE-CHAOS POST-CHAOS
│ │ │ │
Smoke tests Regression suite Baseline capture Regression rerun
Unit tests E2E flows Performance profile Compare baseline
Lint + SAST A11y audit Screenshot baseline Visual diff
Load test (k6) Resilience evidence
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.
- 11d ago First seen · 442 lines · 143 tokens per session scan A 6431d061994e
cloakbrowser-testing is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 143 tokens to every session and 3,333 once invoked, about $0.0007 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
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…