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 agentmods add skills/runbear-io/aweek/recurringnpx skills add runbear-io/aweek --skill recurringgit clone --depth 1 https://github.com/runbear-io/aweekWrote 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/runbear-io/aweek/recurring)<a href="https://agentmods.dev/skills/runbear-io/aweek/recurring"><img src="https://agentmods.dev/badge/skills/runbear-io/aweek/recurring.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.07593 |
| Opus 5 | $0.00017 | $0.03796 |
| Sonnet 5 | $0.00007 | $0.01519 |
| Haiku 4.5 | $0.00003 | $0.00759 |
Grade A, and why
recurring 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 4d 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 — 788 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aweek:recurring
Per-agent recurring-task management. Users define recurrence rules
(daily / weekly / biweekly / monthly with INTERVAL, BYDAY,
BYMONTHDAY, BYSETPOS, COUNT, UNTIL) on an agent. Each rule lives
as a RecurringTask document on disk at
.aweek/agents/<slug>/recurring-tasks.json. Occurrences themselves are
never persisted in the recurring-task store — they are derived from
the rule by the expander on every read:
- Lazily for the SPA calendar (so any ISO week — past, current, future
— can be navigated and rendered without an on-disk
weekly-plans/<YYYY-Www>.jsonfile). - Eagerly by the heartbeat materializer at tick time (so occurrences
are merged into the existing
WeeklyPlanStoreand execute through the same heartbeat loop as hand-authored weekly tasks).
This skill is the CLI surface for the four lifecycle operations
(list / add / update / remove). All persistence and AJV validation lives
in src/storage/recurring-task-store.ts; this skill wraps
src/skills/recurring.ts, which adds friendly pre-flight validation,
auto-derives rec-<slug> ids, stamps createdAt / updatedAt, and
enforces the destructive-operation confirmation gate. Never write
recurring-tasks.json directly — always route through
aweek exec recurring <fn>.
v1 scope
The dispatcher / validators explicitly reject v1-out-of-scope inputs so the failure surfaces here instead of in AJV blob errors downstream:
freqis restricted todaily | weekly | monthly.FREQ=YEARLYis rejected up-front.- Only one rule per RecurringTask — no multi-RRULE composition.
RDATE/EXDATEare not accepted on the rule. Per-occurrence exceptions go through theexceptionsarray (kinds:skiporoverride).- No iCalendar import / export.
If the user asks for any of the above, point them at the v2 backlog and do not extend the skill.
Destructive operation policy
Per project policy, every destructive surface requires explicit
AskUserQuestion confirmation before confirmed: true is passed to the
dispatcher. The underlying validators throw
code: ERECURRING_NOT_CONFIRMED otherwise — do not bypass the gate.
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.
- 4d ago First seen · 788 lines · 35 tokens per session scan A 0bf7743e73a2
recurring is a skill published in the GitHub repository runbear-io/aweek (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 7,593 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…