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 dailyaiagents-cpu/dailyai-os --skill monthly-update-detectorgit clone --depth 1 https://github.com/dailyaiagents-cpu/dailyai-osWrote 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/dailyaiagents-cpu/dailyai-os/monthly-update-detector)<a href="https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/monthly-update-detector"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/monthly-update-detector/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/dailyaiagents-cpu/dailyai-os/monthly-update-detector"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/monthly-update-detector.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.00078 | $0.00545 |
| Opus 5 | $0.00039 | $0.00272 |
| Sonnet 5 | $0.00016 | $0.00109 |
| Haiku 4.5 | $0.00008 | $0.00055 |
Grade A, and why
monthly-update-detector 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 11d 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
monthly-update-detector
Why this exists
Validated finding (cont-19.9-M brief): monthly-updated skills outrank 90-day-stale ones in every skill marketplace tested. So the registry needs to know which skills have decayed. But auto-bumping last_updated to game ranking is fraud — it teaches the system to lie to itself. This skill detects, never edits.
Inputs
--dry-run— count + report path, no writes--digest-only— write Sunday digest from latest 7 daily reports--threshold-days N(default 25) — staleness cutoff--out-dir <path>(default<repo>/data/curator/)
Output
STATUS=ok scanned=<n> stale=<m> threshold_days=<d> report=<path>— daily scanSTATUS=ok mode=digest week_stale=<n> message_path=<path>— Sunday digestSTATUS=ok-dryrun ...- Daily report
data/curator/stale-skills-<YYYY-MM-DD>.md: one line per stale skill, sorted by quality_score descending, with: name, owner_agent, days-since-update, quality_score - Sunday digest
data/curator/stale-digest-<YYYY-MM-DD>.md: ≤15 lines for Telegram
Side effects
- Writes daily and weekly reports
- NEVER edits any SKILL.md, SOUL.md, or run.sh
- NEVER writes to capability-index.json or marketplace.json
- Telegram emission deferred to existing send pipeline (reads
stale-digest-*.md)
Hard rules
- Detection only. No content modification, ever.
- If
data/.well-known/skills/index.jsonis missing, fall back to direct registry walk — never block. - The threshold of 25 days is the warning line. Real refresh prompt fires at 30 days (cron escalates).
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 38 lines · 78 tokens per session scan A b9300f02f4d9
monthly-update-detector is a skill published in the GitHub repository dailyaiagents-cpu/dailyai-os (0 stars, last pushed 4mo ago), licensed MIT. It adds 78 tokens to every session and 545 once invoked, about $0.0004 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-31.
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…