Private RSS Feed
Serve a private RSS feed from a Cloudflare Worker: token-gated, 404-disguised, never a static file.
The Private RSS Feed serves a feed that must stay private: internal changelogs, subscriber-only updates, personal briefings. It is served live from a Cloudflare Worker, gated by a per-feed secret token, never as a static file and never linked with an autodiscovery link tag. A wrong or missing token gets a quiet 404, indistinguishable from "no feed here". The handler reads ?token= from the query string, compares it against the secret stored in the worker's secrets table using a constant-time comparison, and returns 404 'Not found' as plain text on any mismatch. There is no "token exists but wrong" vs "no token" distinction: both are the same 404. A valid token builds the feed live from the database (latest N items, newest first, RFC-2822 dates, XML-escaped content) with a private Cache-Control header so shared caches never store a tokened feed. Because the feed is private, it can carry subscriber-only lines a public feed never would, like yesterday-vs-day-before traffic or unpublished counts. These stay clearly useful and never sensitive. If the stats query errors, the feed still returns valid without the private line: fail-open on extras, never fail-closed on the feed itself. Hygiene is the whole game: no static feed.xml in the build output (one deploy away from being public), no autodiscovery link tag, no token in URLs shared publicly. If the token leaks, you regenerate it with openssl rand -hex 32, update the secret store, redeploy (Pages binds secrets at deploy time), and hand the subscriber the new URL. Never reuse a leaked token.
Version:
Quick answer
Private RSS Feed serves a feed that must stay private — internal changelogs, subscriber-only updates, personal briefings — live from a Cloudflare Worker, gated by a secret token per feed. It is never a static file and never advertised: a wrong or missing token gets the same quiet 404 as no feed at all.
At a glance
| What it is | A token-gated RSS feed served live by a Cloudflare Worker: the token is compared in constant time, and any mismatch returns a plain 404, indistinguishable from a feed that does not exist. |
|---|---|
| Who it's for | Anyone whose feed carries content that should not be public: internal changelogs, subscriber updates, private briefings. |
| What you give it | Your Worker, the feed's secret token (kept in the worker's secrets table), and the items the feed should build from. |
| What you get | A feed URL that only opens with the right token: built live from your data, newest first, properly escaped, with a private cache header so shared caches never store the tokened feed. |
| Works with | Muse — installed by pasting this listing's install prompt, from the Install section below, into a Muse chat. |
| Cost | Free — Skill Harbor House License v1.0. |
| Time | One short setup session in your Worker; the feed then serves itself, and a leaked token is fixed by regenerating it. |
Example — a private briefing feed only subscribers can open
This is an example of the pattern in use, not a promise about your own subscribers or content:
- You publish a weekly briefing to a feed whose URL carries the secret token, and share that URL only with your subscribers.
- A subscriber's reader opens the feed: the worker checks the token in constant time, builds the latest items live from the database, and serves them.
- Someone who finds the bare URL without the token gets a plain 404 — the same answer as a feed that never existed.
Install
Copy the install package below, then paste it into Muse🧪 Sandbox retest pending · Oct 14, 2026📌 Pinned version: commit aeaa0c8Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: none for installing the skill files. No account, no key, no cost. Installing is offline: nothing is sent anywhere during installation, and anything that would ever send data later must be stated before it happens. Install "Private RSS Feed" for me. It serves a private RSS feed from a Cloudflare Worker: the feed is gated by a secret token, a wrong or missing token gets a quiet 404, and the feed is never a static file. Source: https://raw.githubusercontent.com/skill-harbor-hq/house-skills/aeaa0c837868e0972b6cfbfe3d1713b7dde80f23/private-rss-feed/SKILL.md Pinned version: install the code at commit aeaa0c837868e0972b6cfbfe3d1713b7dde80f23 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Helper files, in the same skill folder in the repository (private-rss-feed/): references/worker-feed.md, and LICENSE at the folder root. 1. Download SKILL.md, the helper files and LICENSE into a temporary folder, keeping the helper file inside a references subfolder and LICENSE beside SKILL.md. 2. Compare each file with the fingerprint from Skill Harbor's review of 2026-10-10: - SKILL.md: SHA-256 a2377edf47c570c56021dee61ac5e686d161c3d4b9bb2eff08c1f96a4ab3f0e0 - references/worker-feed.md: SHA-256 ea60286f310858810de08d2cc481d0fd593e34895705e9d92151ddf76ab0692e - LICENSE: SHA-256 d7db27db632a56a432d4f883c89507f031215e665f4806dfcd2dea15c0fb8271 If a file does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. 3. Read the files and tell me in plain words: what the skill does when used, whether it connects to a service, whether it reads or sends any personal information or keys, and anything that seems unusual. 4. When I say yes, copy the files into my skills folder, in a folder named "private-rss-feed", keeping the helper files in their subfolders. 5. Check the copy opens correctly (valid frontmatter, files in place) and tell me what was installed, where, and what is left for me to do: generate my own token and store it in my worker's secret store when I set up a feed. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- aeaa0c8 · 2026-10-13
- Sandbox install test
- Sandbox retest pending · Oct 14, 2026
- Creator identity
- Verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
More house skills
This skill is made by Skill Harbor itself. See all house skills →
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.