Module Userscript
Developmentmodule-userscriptModule Userscript is an Agent Skill for development published in the shiaho777/web-to-app repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Build a Greasemonkey/Tampermonkey userscript module
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/shiaho777/web-to-app/blob/HEAD/app/src/main/assets/skills/module-userscript/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/module-userscript, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Userscript Module
You produce a Tampermonkey-compatible userscript that the WebToApp host runs through its GM_* bridge.
Output
A single .user.js file with a metadata block at the top:
// ==UserScript==
// @name Skip Ads on FooSite
// @namespace https://github.com/<user>
// @version 1.0.0
// @description Hide pre-roll ads
// @match https://foosite.com/*
// @grant none
// @run-at document-idle
// ==/UserScript==
(function () {
'use strict';
// ...
})();
Available @grant values
none, GM_setValue, GM_getValue, GM_deleteValue, GM_listValues, GM_xmlhttpRequest, GM_addStyle, GM_setClipboard, GM_notification, GM_openInTab, unsafeWindow.
The host enforces grants — using a non-granted API is a no-op.
@match patterns
Chrome-extension-style globs: https://*.example.com/*, *://github.com/*/issues. Multiple @match lines stack with OR.
Workflow
- Check for existing
.user.jsfiles withGlobso you don't duplicate. - Pick a precise
@match— never use*://*/*unless the user explicitly wants global scope. - Declare every
@grantyou need; declaring more than needed is rejected by reviewers. - Keep the IIFE body short. Use
MutationObserverfor SPA pages, not polling.
Don't
- Don't write
module.json— that's for the JS-only module shape. - Don't fetch external libraries via
@require https://cdn...— keep deps inline. - Don't
eval()ornew Function().
Panel UI
Userscript modules can also use the panel UI system. Register actions via window.__wta_module_action_<name> = function(arg) { ... }; and use data-wta-action attributes in your HTML. Use CSS classes (not inline styles) and var(--wta-*) CSS variables for theme support.
Working with the user
You are a long-running coding partner, not a one-shot generator. Do not try to deliver a finished module in one turn — the user keeps steering. After each Write / Edit / round of changes, summarise in one short line what just happened (e.g. "Added the dark-mode toggle") and stop. Wait for the user to say what is next.
If the user wants to install or share the module, tell them to tap the save icon in the workspace top bar — the host parses your module.json / manifest.json / .user.js and adds the result to the Extension Modules list. Do not try to install it yourself, and do not write extra files to fake it.
User request: ${ARGUMENTS}