How to Install scripts? (Click here)
If you like my work, please consider supporting it! (Cryptos / Patreon / Ko-Fi / BuyMeACoffee https://cyber-sec0.github.io)
This powerful script automatically monitors any website for changes in its content. It can handle simple text updates, changes in lists, and even complex pages that require POST requests and dynamic security tokens (nonces/CSRF). When a change is detected, the script will automatically open the website in a new tab to notify you.
How to Use
The entire script is managed through a central settings page. Once the script is installed, you can add, edit, and remove sites to be monitored.
1. How to Open the Settings Page
After installing, you can access the settings page at any time from your browser's Tampermonkey menu.
- Click the Tampermonkey extension icon in your browser's toolbar.
- Under "Enabled Scripts", you will see "Website Changes Monitor".
- Hover over it and click "Add/Remove Website". A new tab will open with the settings page.
The Settings Panel
This is where you'll configure each website you want to monitor.
Core Settings
Name: A friendly name for your monitor so you can easily identify it (e.g., "Greasy Fork Forum").
Endpoint URL: The exact web address the script will check for changes. This can be a regular website URL or a specific API endpoint.
Website to Open (Optional): The URL that will be opened in a new tab when a change is detected. If you leave this blank, the script will open the "Endpoint URL" by default.
Comparison Methods
This is the most important setting, as it tells the script *how* to detect a change.
Text/HTML Change (Default): The script will compare the text content of the page (or the selected element). It alerts you if any text is added, removed, or changed. This is best for monitoring news articles, product descriptions, or stock statuses.New Items: The script checks for new items appearing inside a list. It does this by keeping a list of unique IDs for each item. It will only alert you when an item with a new, previously unseen ID appears. This is perfect for monitoring forum threads, comment sections, or lists of new products.Order Change: The script monitors the order of items in a list. It will alert you if the sequence of items changes, even if the items themselves are the same. This is useful for tracking ranked lists, search results, or leaderboards.
Selector & ID Attribute (For List Monitoring)
These fields are used for the "New Items" and "Order Change" methods.
Selector: A CSS Selector that targets the list of items you want to monitor. For example, to monitor posts on a forum, you might use .post-container or li.post.
ID Attribute: The HTML attribute that uniquely identifies each item in the list. Common examples include id, data-id, or data-post-id. You can also type innerText here to use the item's visible text as its unique ID.
Advanced: POST Requests & Dynamic Tokens
Some websites load content dynamically using POST requests, often protected by temporary tokens. This script can handle that.
Headers: Enter any required request headers as a JSON object. For example: {"Content-Type": "application/json"}
Body: The data to be sent with the POST request. You can use a placeholder for a dynamic token here.
Dynamic Token Fetching:
If the site you're monitoring requires a fresh token (like a nonce or CSRF token) for each request, check the "Enable Dynamic Token Fetching" box.
- Token Fetch URL: The URL the script will visit first to grab the token. This is often the main page that contains the search form.
- Token Selector: The CSS Selector to find the element containing the token. Often, tokens are found inside a
<script> tag or a hidden <input> field. - Token Attribute (Optional): If the token is in an attribute (e.g.,
<input value="TOKEN">), specify the attribute name here (e.g., value). Leave blank to get the element's text content. - Token RegEx (Optional): If the token is mixed in with other text (common in
<script> tags), provide a Regular Expression with one capture group to extract it. Example: "nonce":"(.*?)" - Token Placeholder: A unique string you've placed in the "Body" or "Headers" that will be replaced with the real token before the check is performed. Example:
%%NONCE%%
Practical Examples
Example 1: Monitor a Product Stock Status
Let's say you want to know when a product on a shopping site changes from "Out of Stock" to "In Stock".
- Find the product page URL. Use your browser's Developer Tools (F12) to inspect the stock status element and find its unique selector (e.g.,
#stock-status or .product-availability). - Name:
My Product Monitor - Endpoint URL:
https://example-shop.com/product/1 - Comparison Method:
Text/HTML Change - Selector:
#stock-status
The script will now only check the content of the element with the ID "stock-status". When it changes, you'll be notified.
Example 2: Get Notified of New Greasy Fork Scripts
Let's monitor a search result on Greasy Fork for newly updated scripts.
- Go to the search page you want to monitor.
- Inspect the list of scripts to find the selector for each list item (e.g.,
li[data-script-id]) and the attribute that holds its unique ID. - Name:
New Greasy Fork Scripts - Endpoint URL:
https://greasyfork.org/en/scripts/by-site/example.com - Comparison Method:
New Items - Selector:
li[data-script-id] - ID Attribute:
data-script-id
The script will now only alert you when a script you haven't seen before appears on that page.
