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/jsattler/agentic-productivity/weekly-summarynpx skills add jsattler/agentic-productivity --skill weekly-summarygit clone --depth 1 https://github.com/jsattler/agentic-productivityWrote 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/jsattler/agentic-productivity/weekly-summary)<a href="https://agentmods.dev/skills/jsattler/agentic-productivity/weekly-summary"><img src="https://agentmods.dev/badge/skills/jsattler/agentic-productivity/weekly-summary.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.00043 | $0.01290 |
| Opus 5 | $0.00022 | $0.00645 |
| Sonnet 5 | $0.00009 | $0.00258 |
| Haiku 4.5 | $0.00004 | $0.00129 |
Grade A, and why
weekly-summary 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Summary Skill
Generate a comprehensive summary of a week's worth of daily notes.
When to Use
Use this skill when:
- User asks "Summarize this week" or "What happened this week?"
- User requests a weekly review
- User asks for accomplishments or progress over the week
- End of week review requested
Instructions
1. Determine Date Range
If user specifies dates: use those dates.
If user says "this week": calculate the current week (Monday-Sunday or user's preferred week start).
If user says "last week": calculate the previous week.
Default: Use the most recent 7 days including today.
2. Read Daily Notes
For each date in the range:
- Read
notes/YYYY-MM-DD.md - If a file doesn't exist, note it but continue with other days
- Collect all content from all available daily notes
3. Aggregate Information
Across all notes, identify:
Major Themes:
- What were the main focus areas?
- What projects or topics appeared most?
- Any patterns in activities?
Accomplishments:
- Completed tasks (checkbox items marked
[x]) - Milestones reached
- Decisions made
- Problems solved
People Engaged:
- List all people mentioned across all notes
- Count frequency of mentions
- Note context of significant interactions
Ongoing Work:
- Open action items (checkbox items marked
[ ]) - Recurring themes or concerns
- Work in progress
Key Decisions:
- Important choices made
- Direction changes
- Commitments
Insights & Reflections:
- Notable learnings or observations
- Personal growth or realizations
- Ideas generated
4. Generate Summary
Format the output as:
# Weekly Summary: [Date Range]
**Period**: [Start Date] to [End Date]
**Notes Available**: [X] of [Y] days
## Overview
[2-3 sentence high-level summary of the week]
## Major Themes
- [Theme 1]: [Brief description]
- [Theme 2]: [Brief description]
## Key Accomplishments
- [Accomplishment 1]
- [Accomplishment 2]
- [Accomplishment 3]
## People Engaged
- [Person 1]: [Context - e.g., "3 meetings, discussed project X"]
- [Person 2]: [Context]
## Important Decisions
- [Decision 1]
- [Decision 2]
## Ongoing Action Items
- [ ] [Open task 1]
- [ ] [Open task 2]
## Insights & Learnings
- [Insight 1]
- [Insight 2]
## Next Week Focus
[1-2 sentences suggesting priorities based on the week's content]
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 · 229 lines · 43 tokens per session scan A 87f89d6d58e8
weekly-summary is a skill published in the GitHub repository jsattler/agentic-productivity (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,290 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-31.
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…