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 makenotion/notion-cookbook --skill weekly-project-digestgit clone --depth 1 https://github.com/makenotion/notion-cookbookWrote 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/makenotion/notion-cookbook/weekly-project-digest)<a href="https://agentmods.dev/skills/makenotion/notion-cookbook/weekly-project-digest"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/weekly-project-digest/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/makenotion/notion-cookbook/weekly-project-digest"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/weekly-project-digest.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.00049 | $0.00845 |
| Opus 5.5 | $0.00020 | $0.00338 |
| Sonnet 5.5 | $0.00010 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
notion-weekly-project-digest 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 19d 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 project digest
Explain what changed during the reporting period, why it matters, and what needs attention. Separate observed progress from plans and repeated activity.
Workflow
- Set scope and period. Use the named project or team, audience, reporting period, and delivery destination. Resolve a timezone or date boundary when it changes inclusion. Use the established reporting cadence when available; state any reasonable date assumption. A chat update need not become a Notion page.
- Find evidence and a baseline. Fetch supplied project pages directly. Follow their task and update links or search narrowly for the project's previous digest and relevant sources. Inspect database schemas once before queries or writes. Prefer period- and project-scoped queries, but include known unresolved blockers even when their records were not edited this week. Paginate results needed for complete claims; report unavailable sources or partial coverage.
- Compare, do not merely summarize. Use the evidence rules below. Compare with the previous period's update or a dated snapshot, deduplicating records across views and sources. Trace changed decisions to their supporting notes. Do not infer a historical transition from a current status or last-edited date.
- Write for the audience. Lead with meaningful changes and the current outlook. Include progress, continuing blockers or risks, decisions, and next steps or asks only where supported. Cite the relevant records near material claims. Carry forward unresolved items as continuing, not new. Preserve uncertainty and keep internal-only details out of external updates.
- Deliver or save. For a save request, use the supplied or established updates destination and its actual schema. Check for an existing digest for the same project, period, and audience before creating one; update it on a rerun unless the user requests a separate version. Preserve unrelated commentary. Set the project relation when supported. Verify the write, return its link, and report coverage gaps. Producing a digest does not authorize task changes or messages.
What ships with it
6 files 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.
- 19d ago First seen · 67 lines · 49 tokens per session scan A ed54b98bc6a1
notion-weekly-project-digest is a skill published in the GitHub repository makenotion/notion-cookbook (220 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 845 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-10-06.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…