kiosk-browser-control

Name: kiosk-browser-control
Availability: InStock
Author: Fivents

Configures browser kiosk mode to disable navigation, context menus, and keyboard shortcuts.

Updated Feb 16, 2026

Search Tags:#security #browser #kiosk #totem #kiosk-mode #device-lockdown

Ready to run

npx skills add https://github.com/Fivents/one-id --skill kiosk-browser-control

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiosk-browser-control
Source: https://github.com/Fivents/one-id/tree/main/.claude/skills/kiosk-browser-control
Command: npx skills add https://github.com/Fivents/one-id --skill kiosk-browser-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides practical guidance to lock a browser into a secure kiosk mode on physical totems and public terminals, preventing users from navigating away, accessing system UI, or opening developer tools.

Core Features & Use Cases

Guidance to run browsers in fullscreen/kiosk mode and recommended OS-level flags for stability.
Frontend controls to disable right-click, block key events, and prevent page exit combined with server-side validation to avoid relying on UI-only restrictions.
Use Case: Deploying a check-in totem at an event where the browser must remain locked to the application while still allowing safe administrative updates.

Quick Start

Enable kiosk mode on the totem browser and produce an implementation checklist to disable navigation, context menu, and common keyboard shortcuts.

Frequently Asked Questions about kiosk-browser-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I lock a browser into kiosk mode on a public totem?▼

Locking a browser into kiosk mode requires enabling fullscreen mode on the totem and applying recommended OS-level Chrome flags to restrict user navigation, context menus, and developer tools.

What is the best way to prevent users from exiting a web application on a public terminal?▼

Preventing users from exiting a web application on a public terminal involves blocking keyboard shortcuts and page exits via frontend controls, combined with server-side validation to avoid relying solely on UI restrictions.

How does server-side validation work with kiosk mode browser restrictions?▼

Server-side validation reinforces kiosk mode browser restrictions by verifying application state and user actions on the backend, ensuring security does not depend entirely on frontend UI controls that can be bypassed.

Can I disable right-click and keyboard shortcuts in browser kiosk mode?▼

Yes, you can disable right-click and keyboard shortcuts in browser kiosk mode by implementing frontend controls that intercept and block specific key events and context menu triggers on the totem display.

What OS-level Chrome flags are recommended for stable kiosk mode deployments?▼

Recommended OS-level Chrome flags for stable kiosk mode deployments ensure the browser runs consistently in fullscreen on physical totems while preventing access to underlying system UI and developer tools.

Does browser kiosk mode work for event check-in totems that need administrative updates?▼

Browser kiosk mode works for event check-in totems by keeping the application locked to the screen while allowing safe administrative updates through server-side validation and controlled access mechanisms.