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/teejayen/arc/weekly-reviewnpx skills add teejayen/arc --skill weekly-reviewgit clone --depth 1 https://github.com/teejayen/arcWrote 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/teejayen/arc/weekly-review)<a href="https://agentmods.dev/skills/teejayen/arc/weekly-review"><img src="https://agentmods.dev/badge/skills/teejayen/arc/weekly-review.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.00037 | $0.00766 |
| Opus 5 | $0.00018 | $0.00383 |
| Sonnet 5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
weekly-review 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Review
Comprehensive review across all life areas and projects.
When to Use
- Weekly (suggest: Sunday evening or Monday morning)
- When feeling scattered or overwhelmed
- After returning from break/holiday
- User runs
/review
Execution Steps
Step 1: Get context
date "+%Y-%m-%d %H:%M"
Read current state:
state/focus.mdstate/projects.jsonstate/journal.jsonl(last 7 entries)state/session-context.json
Step 2: Review sessions
List recent sessions (files are named YYYY-MM-DD-HHMM-topic.md):
ls -1 sessions/ | tail -10
Read the recent session files to understand what was explored last week.
Step 3: Check inbox
ls -la inbox/
Flag:
- Item count
- Anything older than 7 days (stale)
- Patterns in what's accumulating
Step 4: Review each area
For each area in areas/:
- What happened this week?
- Any open loops?
- Anything neglected?
Review the life areas defined in user-context.md. Common areas:
- Career - Work status, professional development
- Family - Upcoming commitments, quality time
- Health - Exercise, fitness consistency
- Finance - Any actions needed
- Projects - Side project progress
Step 5: Review projects specifically
Read state/projects.json and for each project:
- What moved forward?
- What's blocked?
- What's the next milestone?
Update state/projects.json with current status.
Step 6: Pattern detection
Query state/journal.jsonl for patterns:
- Which topics keep recurring?
- Energy levels over the week
- Any areas consistently absent?
Step 7: Update focus.md
Rewrite state/focus.md with:
- This week's priorities
- What's on the mind
- Any shifts in focus
Step 8: Generate review document
Create sessions/YYYY-MM-DD-weekly-review.md:
---
title: "Weekly Review: [date range]"
created: YYYY-MM-DD
tags: [review, weekly]
---
# Weekly Review: [start] to [end]
## Summary
[Overall sense of the week]
## By Area
### Career
- [Status/progress/notes]
### Family
- [Status/notes]
### Health
- [Status/notes]
### Projects
[For each project in projects.json:]
#### [Project Name]
- Status: [from projects.json]
- Progress: [what moved]
- Next: [upcoming milestone]
### Other Areas
- [Any notable updates]
## Patterns Noticed
- [Recurring themes from journal]
- [Energy patterns]
- [Neglected areas]
## Wins
- [What went well]
## Open Loops
- [Unresolved items needing attention]
## Next Week Focus
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
## Inbox Status
- Items: [count]
- Stale: [count]
- Action: [process now / schedule time]
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 · 153 lines · 37 tokens per session scan A a0da5736542c
weekly-review is a skill published in the GitHub repository teejayen/arc (5 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 766 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…