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 TheCraigHewitt/cowork-starter-pack --skill weekly-reportgit clone --depth 1 https://github.com/TheCraigHewitt/cowork-starter-packWrote 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/thecraighewitt/cowork-starter-pack/weekly-report)<a href="https://agentmods.dev/skills/thecraighewitt/cowork-starter-pack/weekly-report"><img src="https://agentmods.dev/badge/skills/thecraighewitt/cowork-starter-pack/weekly-report/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/thecraighewitt/cowork-starter-pack/weekly-report"><img src="https://agentmods.dev/badge/skills/thecraighewitt/cowork-starter-pack/weekly-report.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.00075 | $0.01075 |
| Opus 5 | $0.00037 | $0.00537 |
| Sonnet 5 | $0.00015 | $0.00215 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade A, and why
weekly-report 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Report
Turn a week of meetings, messages, and scattered notes into a one-page recap the user can send to themselves, a manager, or a team — without spending 45 minutes writing it.
Before starting
- Read
context/about-me.md— who is this report for, what does the user own? - Read
context/preferences.md— what format does the user want? Who is the audience? - Read
context/voice.md— for any narrative prose in the report. - Check
/output/for last week's report — continuity matters. Did last week's priorities get done?
What to produce
A markdown file saved to /output/weekly-report-{YYYY-MM-DD}.md, covering Monday through today (or a 7-day window if today isn't Friday).
Four sections:
- What moved this week — 3–6 bullets. The wins, the meaningful progress, the decisions made. Specific. No vague "worked on X" — say what shipped, what got decided, what changed.
- What stalled or slipped — 1–4 bullets. Honest. Don't cover things up. If something was on last week's list and didn't happen, say so and say why.
- Decisions & notable changes — decisions taken this week that someone might want to know about later. One line each. (This section feeds a decision log over time.)
- Next week's focus — 3 priorities, ranked. Each with one sentence of why.
Inputs
- Calendar from the last 7 days
- Messages / Slack DMs from the last 7 days
- Last week's weekly report (if exists) — for continuity
- Any
/output/files created this week — these are the trail of work done - Any decision-journal entries in the project folder (if used)
How it works
- Pull the week's calendar — identify meetings that produced outputs (reviews, 1-1s, decisions)
- Pull message/Slack history — look for commitments made, decisions mentioned, items closed
- Scan
/output/for files created/modified this week — this is the actual work trail - Compare to last week's "Next week's focus" — did those priorities move?
- Draft the four sections
- If the user specified an audience in
preferences.mdorabout-me.md, tune the tone to that audience - Save the file, tell the user one-line what was notable
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 · 84 lines · 75 tokens per session scan A 6c5b9ac0abbc
weekly-report is a skill published in the GitHub repository TheCraigHewitt/cowork-starter-pack (5 stars, last pushed 4mo ago), licensed MIT. It adds 75 tokens to every session and 1,075 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
give-me-tips
Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.
suede-onboarding
Suede-affiliated onboarding and activation strategy for first-run sequencing, empty states, setup checklists, activation milestones, time to value, and retention-linked measurement. Use when users sign up but fail to reach first value or the product needs a new first-session flow. NOT FOR: registration optimization…
google-apps-script
Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a…
google-chat-messages
Send Google Chat messages via incoming webhooks — text, rich cards (cardsV2), threaded replies. TypeScript types, card builder utility, widget reference inline. Use whenever the user wants to post to Google Chat from a script, build a chatbot reply, send a notification card, build a Google Chat webhook integration, or…
parcel-tracking
Track parcels and check delivery status for Australian and international couriers. Searches Gmail for dispatch/shipping emails and provides tracking links for all major Australian couriers including AusPost, StarTrack, Aramex, CouriersPlease, Sendle, Toll, Team Global Express, DHL, FedEx, TNT, Hunter Express, Border…
knowledge-base-builder
FAQ identification from support tickets, step-by-step tutorial creation, screenshot/video script guidance, search optimization, and self-service deflection tracking.