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 samkawsarani/sams-product-plugins --skill weekly-updategit clone --depth 1 https://github.com/samkawsarani/sams-product-pluginsWrote 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/samkawsarani/sams-product-plugins/weekly-update)<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/weekly-update"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/weekly-update/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/samkawsarani/sams-product-plugins/weekly-update"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/weekly-update.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.00069 | $0.00961 |
| Opus 5 | $0.00034 | $0.00481 |
| Sonnet 5 | $0.00014 | $0.00192 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
weekly-update 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 10d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Today's date: $TODAY
- Voice guide:
VOICE-GUIDE.md(if present) - Stakeholder preferences:
knowledge/people/ - Goals:
GOALS.md - Past updates:
knowledge/references/stakeholder-updates/(if present)
Step 1: Identify Audience
If the user specified a recipient (e.g. "for CEO", "for board"), note it. Otherwise ask: "Who is this update for?" — one person or a group (e.g. leadership team, board, cross-functional leads).
Read knowledge/people/ for any matching stakeholder preference files. Note what each person cares about and what to avoid.
Step 2: Gather Progress Data
Always read from all available sources and merge:
From Linear (if MCP is connected):
- Pull project status — name, status (on track / at risk / behind), % complete, owner
- Pull initiative status — name, health, which projects roll up under it
- Note any projects that slipped, were completed, or changed status this week
From this repo (always):
- Read
tasks/TASKS.md— completed (- [x]), in progress (- [ ]), and Waiting On items - Read
projects/— scan active project briefs for context and current status - Read
GOALS.md— map all progress to quarterly goals - Read
meetings/— scan recent notes for decisions or outcomes worth surfacing
Merge both sources — Linear gives project/initiative health, repo gives task-level detail and goal alignment. Note if Linear is unavailable.
Step 3: Assess Status
For each active project or initiative:
- On Track — progressing as expected
- At Risk — may slip without action
- Blocked — waiting on something external
Flag anything that needs stakeholder awareness or a specific ask.
Step 4: Draft the Update
Keep it under 500 words. Lead with what matters most to the audience.
Use this structure:
Subject: Product Update — Week of [Date]
**TL;DR**
- [Most important outcome or milestone this week]
- [Key blocker or risk, if any]
- [Top focus next week]
**Progress**
[Initiative or project]: [Status] — [1-line summary of movement]
[Initiative or project]: [Status] — [1-line summary of movement]
**Metrics** *(if available)*
[Metric]: [Current] ([change vs last week], target: [X])
**Blockers & Risks**
[Blocker] — [Proposed next step or ask]
**Next Week**
- [Priority 1, tied to goal]
- [Priority 2, tied to goal]
- [Priority 3]
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.
- 10d ago First seen · 118 lines · 69 tokens per session scan A 1b96bd448bb3
weekly-update is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 961 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.