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 skills add ndunl075/alfred-pennyworth --skill weekly-reviewgit clone --depth 1 https://github.com/ndunl075/alfred-pennyworthWrote 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/ndunl075/alfred-pennyworth/weekly-review)<a href="https://agentmods.dev/skills/ndunl075/alfred-pennyworth/weekly-review"><img src="https://agentmods.dev/badge/skills/ndunl075/alfred-pennyworth/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/ndunl075/alfred-pennyworth/weekly-review"><img src="https://agentmods.dev/badge/skills/ndunl075/alfred-pennyworth/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.00027 | $0.00630 |
| Opus 5 | $0.00014 | $0.00315 |
| Sonnet 5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
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 11d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly review
Overview
Unlike the morning brief (today-focused, fully pre-ranked) or inbox triage (one connector), a weekly review pulls from several sources and needs you to find the throughline yourself -- what actually moved, what's stuck, what's coming up next week.
When to use
- The user asks for a weekly review, retrospective, or "how did this week go."
- A weekly cron trigger (see
cron/connector-health-check.jsonfor the pattern -- a dedicated weekly-review cron entry is not bundled by default; add one only if you want this delivered unprompted).
Steps
- Call
brief_getfor the current state of due/overdue tasks and calendar items. - Call
connector_records_get(connector="github", record_type="notification")for anything GitHub surfaced this week. - Call
connector_records_get(connector="canvas", record_type="missing")if the user has Canvas configured, for missing assignments. - Call
memory_searchwith a query built from the week's obvious themes (project names, course names, recurring topics) to surface anything remembered that the structured connectors wouldn't otherwise show -- commitments made in conversation, not tracked as a formal task. - Synthesize: what got done (
task_completehistory isn't directly queried here today -- infer completion from tasks no longer appearing as open inbrief_get), what's still open and how long it's been open, and what's coming due next week.
Common pitfalls
- Presenting
connector_records_get's raw list as the review -- this skill exists specifically to add the synthesis step 5 that the other two skills deliberately don't attempt. - Treating a memory returned by
memory_searchas more authoritative than a formal task frombrief_getwhen they conflict -- flag the conflict to the user rather than silently picking one. - Running this against a Canvas-less or GitHub-less setup and treating the resulting empty list as an error -- both connectors are optional; report "nothing configured" rather than a failure.
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.
- 11d ago First seen · 67 lines · 27 tokens per session scan A 792a7487d073
weekly-review is a skill published in the GitHub repository ndunl075/alfred-pennyworth (0 stars, last pushed 23d ago), licensed Apache-2.0. It adds 27 tokens to every session and 630 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-31.
Other skills, from other repositories
code-assistant
A Chinese-language workflow for using Claude Code, Codex, or Gemini as background coding agents for complex development tasks. It covers orchestration, monitoring, isolation, review, and recovery.
cron-scheduler
A scheduling guide for creating and managing tasks that run at exact repeating times, such as every day, week, or hour.
daily-manager
A daily planning and coordination guide for organising tasks, priorities, progress reviews, and work that spans several specialist add-ons.
feishu
A guide for operating Feishu, a workplace collaboration platform used for messages, documents, tasks, calendars, and groups.
file-organizer
A file-management guide for sorting, renaming, archiving, finding duplicates, and analysing disk usage.
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks CoWork-OSS to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.