Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add eigent-ai/agent-skills --skill last30daysgit clone --depth 1 https://github.com/eigent-ai/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/eigent-ai/agent-skills/last30days)<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/last30days"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/last30days/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/last30days"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/last30days.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00070 | $0.00449 |
| Opus 5 | $0.00035 | $0.00225 |
| Sonnet 5 | $0.00014 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
last30days scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Last30Days
Overview
Use this skill to produce a grounded brief on a topic using only recent public discussion and engagement signals. Prioritize sources from the last 30 days, rank findings by real engagement, and merge duplicate stories before synthesizing.
Workflow
- Clarify the topic, audience, and output format when they are not obvious.
- Search relevant public platforms for the last 30 days:
- Reddit, Hacker News, GitHub, X, YouTube, and Polymarket when relevant.
- Topic-specific communities, handles, hashtags, repos, and keywords.
- Capture engagement context such as upvotes, comments, stars, views, reposts, or prediction odds.
- De-duplicate repeated stories across platforms and keep the strongest source links.
- Rank findings by engagement and relevance, not by editorial placement.
- Produce a concise brief with:
- Executive summary.
- Top themes and ranked evidence.
- Notable disagreements or weak signals.
- Source links and dates.
- Practical implications for the user's decision.
- If the user asks for
--emit=html, produce a formatted HTML brief. - If the user asks for ELI5 after a run, rewrite the same findings in plain language without changing the evidence.
Example Prompts
/last30days new claude code agent skills github trending- find what skills are gaining traction this week across HN, Reddit, and GitHub./last30days Notion vs Obsidian knowledge management 2026- summarize what people are actually saying across Reddit and X, ranked by engagement./last30days AI writing tools market sentiment --emit=html- synthesize discussion from HN, X, and Polymarket into a shareable brief.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 35 lines · 70 tokens per session scan A 3a12ed53f61f
last30days is a skill published in the GitHub repository eigent-ai/agent-skills (19 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 449 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…