Screen Capture: What Works, What Is Theatre
Hardware DRM, per-session watermarking and FLAG_SECURE - and an audit that names the anti-screenshot code that stops nobody.
$39
Works with the AI Agents you already use
Screen Capture: What Works, What Is Theatre
Example session with this skill installed
Audit my current site in ./src and give me a plan to protect my premium video content and traceable document viewer.
- Read your context and instructions
- Compiled the screen capture
I have audited the ./src directory. The existing protection relies on disabling right-click and user-select: none, which is categorized as
THEATRE and provides zero security.
Protection Strategy
| Component | Recommended Measure | Implementation Goal |
|---|---|---|
| Premium Video | Hardware DRM (EME) | Block capture via HW_SECURE_ALL |
| Document Viewer | Per-session Watermarking | Make leaks traceable to account/timestamp |
| Android Access | FLAG_SECURE | Hardware-level blocking for all app content |
| iOS Access | isCaptured Detection | Log capture events and blank mirrored views |
Forensic Watermark Implementation
// Server-side: Generate unique stamp
const stamp = `${user.id}-${session.id.slice(0, 8)}-${new Date().toISOString()}`;
// Client-side: Overlay implementation
const wm = document.createElement('div');
wm.setAttribute('aria-hidden', 'true');
wm.style.cssText = `position:fixed;inset:0;pointer-events:none;z-index:9999;
opacity:.10;font:12px monospace;color:#000;white-space:pre;overflow:hidden;
transform:rotate(-24deg) scale(1.6);user-select:none`;
wm.textContent = (stamp + ' ').repeat(400);
document.body.appendChild(wm);
Video Protection (EME)
const access = await navigator.requestMediaKeySystemAccess('com.widevine.alpha', [{
initDataTypes: ['cenc'],
videoCapabilities: [{
contentType: 'video/mp4; codecs="avc1.640028"',
robustness: 'HW_SECURE_ALL'
}]
}]);
Next steps
- Replace the existing
oncontextmenublocks with the forensic watermark script. - Integrate a Widevine or FairPlay license server to support the EME hardware robustness check.
- Update your Android manifest and Activity code to set
FLAG_SECURE.
Connects securely to your tools. The creator never sees your data.
About this skill
A web page cannot block a screenshot. Here is what you can actually do.
Protect content against screen capture with what actually works - hardware DRM for video, per-session forensic watermarking for everything else, FLAG_SECURE in a native Android wrapper, signed short-lived URLs - and remove the anti-screenshot theatre that stops nobody and breaks accessibility. Use when a site hosts paid, confidential or pre-release content, when someone asks to "block screenshots", or before buying an anti-capture product.
Start from the truth: there is no browser API to prevent a screenshot. The operating system captures the framebuffer and never tells the page. Disabling right-click, trapping the PrintScreen key, detecting devtools, blurring on window blur - all of it is bypassed by a phone pointed at the screen, and it breaks screen readers and text selection on the way. So the goal changes: prevent where it is technically possible, and make everything else traceable.
Integration is spelled out with the code: a ten-line per-session watermark that is aria-hidden and pointer-events none; the EME call with HW_SECURE_ALL and why you must fail closed instead of falling back to software; FLAG_SECURE in Kotlin, which also covers a WebView; the iOS capture notification and isCaptured, which detect but cannot prevent; signed short-lived URLs; and a CI gate.
Includes an EXPERT.md reference (exact parameters, thresholds, failure diagnosis): the platform truth table, Widevine and PlayReady robustness levels, watermark parameters that survive cropping and re-encoding, the session log that makes a watermark resolvable, what each theatre measure costs in accessibility, a threat model that matches budget to risk, and a vendor procurement checklist.
Tested scripts: scripts/audit_capture.py - it scans a codebase and sorts every measure into REAL, DETERRENT or THEATRE, says what each one actually does and where it is, and exits non-zero when the protection is theatre only. Verified on three fixtures: a theatre-only codebase scores 6 theatre and 0 real and fails; a DRM plus FLAG_SECURE codebase scores 3 real; a mixed one reports both. JSON output for CI.
Acceptable use: protecting paid, confidential, embargoed or licensed content on a service you operate, with the protection disclosed. The skill refuses defeating accessibility tools, preventing a person from recording evidence of fraud, abuse or unsafe conditions, blocking operating-system features outside your own window, fingerprinting users under cover of capture detection, and watermarking people rather than content.
It will not block screenshots in a browser, because nothing does, and it will not promise a client something a phone camera defeats.
Cannot block browser screenshots for non-video content. DRM requires a license server. iOS only supports post-capture detection, not prevention. Native wrappers required for FLAG_SECURE.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 27 days ago
Requires