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/shdennlin/agent-plugins/weeklynpx skills add shdennlin/agent-plugins --skill weeklygit clone --depth 1 https://github.com/shdennlin/agent-pluginsWhat 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.00086 | $0.00839 |
| Opus 5 | $0.00043 | $0.00419 |
| Sonnet 5 | $0.00017 | $0.00168 |
| Haiku 4.5 | $0.00009 | $0.00084 |
Grade A, and why
digest:weekly 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 yesterday.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Digest
Synthesize git activity across multiple projects into a themed recall report — what you actually worked on, fixed, refactored, and explored. Designed for recall (memory aid), not enumeration (commit dumps).
Usage
$weekly # past 7 days, projects from config
$weekly 14 # past 14 days
$weekly last week # previous Mon-Sun
$weekly since friday # natural-language range
$weekly 2026-05-10..2026-05-17 # explicit range
$weekly may # whole month
$weekly 7 --projects
- /Users/me/project-a
- /Users/me/project-b # inline project list
$weekly --write # save to $WEEKLY_DIGEST_DIR
$weekly 30 --detail # past month + chronological list
Options
| Flag | Description |
|---|---|
--projects <list> |
Markdown bullet list of project paths (multi-line) |
--config <path> |
Custom config file (default: ~/.claude/digest-projects.json) |
--author <email> |
Filter by author email. Default: your git email. all for everyone. |
--brief |
Short summary only |
--detail |
Include full chronological commit list |
--write |
Save to $WEEKLY_DIGEST_DIR (or ./Weekly/ if env var unset) |
--out <file> |
Save to custom path |
Environment Variables
WEEKLY_DIGEST_DIR— Output directory for--write. Set in your shell rc:export WEEKLY_DIGEST_DIR="$HOME/Documents/vault/Weekly"
Project List Resolution
In order of precedence:
--projectsinline bullet list--config <path>JSON file~/.claude/digest-projects.json- Error with example config
Config format:
{
"projects": [
{ "path": "/Users/me/project-a", "name": "project-a" },
{ "path": "/Users/me/project-b" }
]
}
Architecture
This skill follows the script + thin command + judgment-focused agent pattern (see ralph-loop for the canonical example):
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 84 lines · 86 tokens per session scan A d188d6a120d0
digest:weekly is a skill published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 86 tokens to every session and 839 once invoked, about $0.0004 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…