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/calendarnpx skills add runbear-io/aweek --skill calendargit 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/calendar)<a href="https://agentmods.dev/skills/runbear-io/aweek/calendar"><img src="https://agentmods.dev/badge/skills/runbear-io/aweek/calendar.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.1 | $0.00018 | $0.01633 |
| Opus 5 | $0.00009 | $0.00816 |
| Sonnet 5 | $0.00004 | $0.00327 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
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 6d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aweek:calendar
Display an agent's weekly plan as a calendar grid with day columns and hour rows. Tasks are numbered so users can ask about any task by number.
Instructions
You MUST follow this exact workflow when this skill is invoked.
Step 1: Select an Agent
List all available agents:
aweek exec calendar listAgentsForCalendar
The call returns a JSON array of { id, name, role } records. Treat an
empty array as the no-agents case.
- If no agents exist, inform the user: "No agents found. Use /aweek:hire to create one first." and stop.
- If only one agent exists, auto-select it.
- If multiple agents exist, ask the user to pick one using AskUserQuestion.
Step 2: Resolve the Week (optional)
If the user didn't mention a specific week, skip this step and go to Step 3 — the renderer defaults to the agent's latest approved plan.
If the user mentioned a week (e.g. "week 17", "the week of April 20", "next
week", "2026-W14"), pass that string verbatim to loadAndRenderGrid as a
week field — it accepts every shape below — or pre-resolve it to the
canonical YYYY-Www so you can confirm the choice in your reply:
echo '{ "input": "next" }' | aweek exec calendar resolveWeekKey --input-json -
Accepted shapes:
| Input | Meaning |
|---|---|
2026-W17 |
Canonical ISO week (case-insensitive W) |
2026-04-20 |
Any ISO date — derives the ISO week containing it |
17 or W17 |
Bare week number — uses the current ISO year (in the project time zone) |
current, this, now |
Current week |
next |
Next ISO week |
prev, previous, last |
Previous ISO week |
Invalid input throws — the skill should surface the error message and re-ask.
Step 3: Render the Calendar Grid
The default output is a GitHub-flavored markdown table (format: "markdown").
Claude Code's terminal UI re-flows pipe tables to the available width, so the
calendar expands / contracts with the window instead of sitting in a fixed
120-column box. Pass format: "box" only when the host cannot render markdown
tables (e.g. raw log tails) — the Unicode box-drawing grid still works but its
columns are fixed.
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.
- 6d ago First seen · 139 lines · 18 tokens per session scan A 073b8a7df46d
calendar is a skill published in the GitHub repository runbear-io/aweek (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,633 once invoked, about $0.0001 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…