Independent AI intelligence Two editions daily · ET
Fervor AI

Analysis · November 17, 2026 · repo

mvanhorn/last30days-skillai-skillsprivacyagent-securityclaude-code

last30days Turns Reddit, X and YouTube Into One AI Research Brief. Decide What It Can Read First.

A research skill for coding agents with about 68,600 GitHub stars ranks the web by upvotes and money. Its smartest feature is the question it asks before it touches your browser.

Search engines are slow to notice what people are arguing about this week.

A new tool ships on a Tuesday. By Thursday the Reddit thread has 900 comments, the Hacker News post has a fight in it, three YouTubers have tried it on camera, and the top Google result is still the launch press release. If you want the real picture, you open twelve tabs and read for an hour.

That gap is why mvanhorn/last30days-skill has drawn about 68,600 GitHub stars (per the GitHub API on the morning of November 17, 2026), with v4.3.0 released on November 16. You type /last30days and a topic. Your coding agent searches Reddit, X, YouTube, Hacker News, Polymarket, GitHub and more for the last 30 days, then writes one brief.

The pitch is the README's tagline: "An AI agent-led search engine scored by upvotes, likes, and real money - not editors."

Here's the part the pitch skips. The most useful sources only open up when you hand the tool your own accounts: API keys, and for some sources the login cookies sitting in your browser. So the real decision with last30days isn't whether it finds good stuff. It does. The decision is what you let it read, and the project gives you better tools for that decision than most skills do.

What it is, in plain terms

An agent skill is a folder of instructions and scripts that a coding agent (Claude Code, Codex, Cursor, Gemini CLI and others) loads when a task calls for it. last30days is one of those, MIT licensed, with a Python engine.

When you run it, the README describes roughly seven steps. The agent figures out who matters for your topic (the founder's X handle, the right subreddit, the GitHub repo). It searches all the sources in parallel. It scores what it finds by engagement, relevance and freshness. It merges the same story told in three places into one item. Then it writes a brief with the receipts: upvote counts, quoted comments, prediction-market odds, release notes.

Some sources work with zero setup. Per the README, Reddit with comments, Hacker News, Polymarket and GitHub need nothing, and so do patent filings and careers pages when your topic is a company. Everything else needs something from you.

The scoring idea, and where it bends

The core idea is that attention is evidence. The README puts it plainly: "A Reddit thread with 1,500 upvotes is a stronger signal than a blog post nobody read." Polymarket odds, it adds, are "backed by real money and insider information."

That idea is useful and limited in the same breath.

Engagement tells you what people care about. It does not tell you what is true. A wrong take with 2,000 upvotes can outrank a correct one with 40. A product with a loud fan base looks bigger than a better one that people use at work and never post about. And the sources skew toward people who post a lot, which is a specific slice of humanity.

So use last30days for what it is good at: finding the arguments, the complaints and the names you hadn't heard yet. Then check the claims that matter against a primary source, the same way you would after reading the threads yourself. The brief is a map of the conversation, not a ruling on it.

The real decision: what it can read

Here is where the project earns more trust than its marketing needs to.

The extra sources come through what the README calls bring your own keys. A Brave Search key adds web search (2,000 free queries a month). A ScrapeCreators key adds TikTok, Instagram, Threads, Pinterest, LinkedIn and YouTube comments (10,000 free calls, then pay as you go). For X, you can set an official API token, or you can simply be logged into x.com in your browser, and, once you say yes, the tool reads your session cookies. Cookies are the small files that keep you signed in. Whoever holds them can act as you on that site.

The project treats that as a real permission, not a setup detail. Its configuration docs lay out consent points that the agent walks you through on the first run:

  • Browser cookies. The agent asks before reading anything, and says the permission covers later runs too. On macOS it checks Chrome and other Chromium browsers first, then Firefox and Safari. On Windows and Linux its built-in cookie scan supports Firefox only.
  • Reddit as you. A separate question. The docs say outright that searching Reddit as your logged-in account "may breach Reddit's terms."
  • X scraping. The free X path uses your browser cookies, and the docs warn that "scraping carries some account risk."

It also ships two switches I wish every skill had. --preflight reports what a run would do (where config comes from, the browser-cookie plan, planned file writes, which sources are available) without reading cookies, writing files or researching anything. --no-browser-cookies hard-disables cookie reading for a run. When the skill runs as an MCP server (a plug-in that gives agents tools), cookie reading is denied by default, and turning it on still needs the separately recorded consent.

That's the right shape. A tool that borrows your logins should show its plan before it touches them, and this one does.

Two modes worth knowing

Most people use last30days on a topic they name: a person before a meeting, a company before a sales call, a library before adopting it. There is a second mode that is more useful for builders. Ask /last30days what's exploding in AI agents? and it switches to discovery. The engine sweeps the hot lists first (Reddit's r/all, the Hacker News front page, Digg), your agent judges the nominations, and each survivor gets a full research pass that can include X and your other sources. The README promises 5 to 10 momentum-ranked topics. The skill's own discovery runbook is more honest about slow weeks: it treats "Nothing solid this window" as a valid result.

If you want to plug it into a workflow instead of reading briefs, ask for machine-readable JSON. The README says that returns "the stable, versioned agent profile," which is the piece to build on if you are wiring this into an n8n flow (a visual automation tool) or a nightly agent run.

Where your data goes

The README's data handling section is short and worth reading in full. By default the skill runs on your machine and nothing leaves except calls to the search services you use.

One opt-in changes that. If you set a reasoning provider key (OpenAI, xAI, OpenRouter or Google), the engine sends your research topic and the snippets it retrieved to that provider for relevance scoring. Without one, it falls back to a local scoring model. Your agent host still sees everything, of course, since your coding agent writes the brief.

Runs through the skill save reports to ~/Documents/Last30Days/ by default. If you add --store, findings also go into a local SQLite database (research.db in the save folder, or under ~/.local/share/last30days/ if there isn't one), and the docs say it is not uploaded anywhere.

Put this into practice

Here's the low-risk way to try it.

1. Install it. In Claude Code:

/plugin marketplace add mvanhorn/last30days-skill
/plugin install last30days

For Codex, Cursor, Copilot, Gemini CLI and other Agent Skills hosts:

npx skills add mvanhorn/last30days-skill -g

The -g flag installs it for your user across all projects. Pick one install method in Claude Code; the README notes that having both active shows /last30days twice. The engine needs Python 3.12 or newer.

2. Look before it reads. From the installed skill folder, run:

python3 scripts/last30days.py --preflight

You'll get the plan: which sources are on, whether it intends to read browser cookies, and where it will write files. Nothing is read or researched.

3. Do your first run with no cookies. Ask /last30days about a topic you already know well, and say no to the browser-cookie and Reddit-session questions. Reddit, Hacker News, Polymarket and GitHub still work. Because you know the topic, you can judge how good the brief is before you give it anything more.

4. Add keys one at a time. A Brave Search key is a cheap next step. On macOS you can keep keys in the system Keychain instead of a .env file with the bundled scripts/setup-keychain.sh. Add X cookies only if X is where your topic actually lives, and consider using a browser profile that isn't logged into accounts you care about.

5. Check one claim per brief. Pick the most surprising number or quote in each brief and open the source it cites. If it holds up a few times in a row, you've learned how far to trust it. If it doesn't, you've learned that faster than a month of skimming would teach you.

Honest limitations

Popularity is not accuracy. The ranking rewards what got attention. Treat the brief as leads.

Your accounts carry the risk. Cookie-based X access and Reddit-as-you can run against those platforms' rules, by the project's own description. The account at risk is yours.

Coverage depends on what you pay for. The free sources are good. TikTok, Instagram and LinkedIn need a ScrapeCreators key, Perplexity is pay as you go, and the official X API covers only about the last week unless your developer project has full-archive access.

The README is a sales page. Its big claims about what no other AI can search, and the example briefs, are the author's own showcase. The useful facts are in CONFIGURATION.md and the data handling section, so read those.

It moves fast. The README itself warns that "your installed version may differ." v4.3.0 shipped November 16, and the main branch had new commits within hours. Recheck anything here against the version you install.

The takeaway

last30days solves a real problem: the freshest information about almost any tech topic lives in comment threads that search engines index late and badly. Judging by its docs, it is built with more care than most skills in its category.

The skill that matters isn't the install. It's the thirty seconds you spend on --preflight and the consent questions, deciding what an agent may read on your behalf. This project makes that decision easy to see. So before your first /last30days, run --preflight, say no to cookies, and add access one source at a time. Take the decision on purpose, and the brief becomes a tool you can trust for exactly what it is.

Sources: mvanhorn/last30days-skill README and CONFIGURATION.md (main branch, read November 17, 2026; latest release v4.3.0, November 16, 2026); releases; star count from the GitHub API, November 17, 2026.