Borrowing it
Nothing to install: this file belongs to chacosoldier/compabob. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chacosoldier/compabob/main/.claude/skills/weekly-review/SKILL.mdgit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/chacosoldier/compabob/weekly-review)<a href="https://agentmods.dev/skills/chacosoldier/compabob/weekly-review"><img src="https://agentmods.dev/badge/skills/chacosoldier/compabob/weekly-review/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/chacosoldier/compabob/weekly-review"><img src="https://agentmods.dev/badge/skills/chacosoldier/compabob/weekly-review.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.00484 |
| Opus 5.5 | $0.00022 | $0.00194 |
| Sonnet 5.5 | $0.00011 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00048 |
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 1mo 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.
What it actually says
Weekly Review
Produce a terse end-of-week summary that captures what changed and what is still owed.
Steps
-
Determine the Week. Confirm the ISO week (e.g.
2026-W21). Usedateor theinject-nowhook. -
Gather inputs. Read:
vault/Daily/: all daily notes from Monday through today (or the last 7 days). Pull## Priorities,## Completed, and any## Reflectionsections.vault/Decisions/: any decision records dated this week.memory/topics/: entries modified this week (checkmemory/MEMORY.mdfor the index).- If meeting notes exist in
vault/, scan recent ones for open action items.
-
Synthesize five sections:
- Done: what was completed (shipped, merged, decided, closed).
- Slipped: what was planned but not done; carry-forward items.
- Decisions: key decisions made (link to
vault/Decisions/files). - Owed to others: commitments the user owes to someone else.
- Owed to self: commitments the user made to themselves.
-
Propose top 3 priorities for next week. Base them on the slip-list and the most consequential pending commitments. One sentence each.
-
Write to vault (optional). Ask the user; if they approve, write to
vault/Weekly/YYYY-WW.md.
Output
Lead with one sentence summarising the week. Then:
## Weekly Review: YYYY-WW
**Done**
- ...
**Slipped**
- ...
**Decisions**
- ...
**Owed to others**
- ...
**Owed to self**
- ...
### Next week's top 3
1. ...
2. ...
3. ...
Terse and scannable. Omit any empty section. End with no closing line.
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.
- 1mo ago Changed 4ece1da767f8
- 1mo ago First seen · 61 lines · 54 tokens per session scan A 823df29b81ae
weekly-review is a skill published in the GitHub repository chacosoldier/compabob (34 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 484 once invoked, about $0.0002 per session on Opus 5.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
meeting-notes
Use when the user asks to capture, structure, or summarize meeting notes / call notes / 1:1 discussion / standup notes. Produces a standard template with attendees, agenda, decisions, action items (owner + deadline), and open questions.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).
inbox-cleanup
Run a high-recall, multi-pass email inbox cleanup. Pattern-based subject queries catch 25x more archivable email than sender scans alone. Includes urgency triage, classification signals, and post-cleanup filter setup.
inbox-management
Ongoing Gmail inbox management via scheduled runs. Archives known noise, flags urgent items, drafts replies in-thread (never auto-sends), and catches stale follow-ups. Empty polls spend no model tokens. Starts in flag-only mode.
notifications
Send notifications through the unified notification router.