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 asodevapp/skills --skill seasonal-calendargit clone --depth 1 https://github.com/asodevapp/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/asodevapp/skills/seasonal-calendar)<a href="https://agentmods.dev/skills/asodevapp/skills/seasonal-calendar"><img src="https://agentmods.dev/badge/skills/asodevapp/skills/seasonal-calendar/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/asodevapp/skills/seasonal-calendar"><img src="https://agentmods.dev/badge/skills/asodevapp/skills/seasonal-calendar.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.00054 | $0.01207 |
| Opus 5 | $0.00027 | $0.00603 |
| Sonnet 5 | $0.00011 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
seasonal-calendar 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seasonal ASO Calendar
Use this for holiday-driven ASO planning, seasonal keyword opportunities, campaign timing, metadata changes, screenshot theming, In-App Events, and revert plans.
Source
ASO.dev publishes an App Store marketing calendar with public holidays and seasonal planning links:
https://aso.dev/blog/calendar/- Google Calendar subscription is available from that page.
- Apple Calendar / Outlook subscription is also available from that page.
This calendar is a planning source, not MCP and not the ASO.dev product API.
Workflow
- Identify target countries, locales, app category, and planning horizon.
- Use the ASO.dev calendar to find relevant public holidays, cultural moments, and seasonal windows.
- Pick only moments that fit the app and market. Do not force every holiday into every app.
- For each moment, decide whether the app has a real seasonal use case, content angle, or user intent.
- Research or request keyword data before changing indexed metadata.
- Turn each relevant moment into one or more actions:
- In-App Event
- CPP/PPO variant
- screenshot refresh
- promotional text or What's New
- keyword tracking and metadata test
- localization QA
- Add lead time:
- 4-6 weeks for creative planning
- 2-3 weeks for localization and assets
- at least several days before App Review-sensitive submissions
- Use
in-app-events,cpp-ppo-pages,screenshot-brief,metadata-editor,keyword-coverage, orlocalization-cross-localizationfor execution.
Seasonal ASO principles
- Seasonal rankings are competitive and time-sensitive.
- Plan indexed metadata changes before the event peak; do not wait until the day of the event.
- Revert seasonal metadata after the peak unless the seasonal terms continue to perform.
- Promotional text is the safest field for fast seasonal messaging because it does not require a new app version.
- Never sacrifice a high-performing evergreen keyword for a speculative seasonal term.
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 · 136 lines · 54 tokens per session scan A 7833bfcaaca8
seasonal-calendar is a skill published in the GitHub repository asodevapp/skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,207 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-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…